diff --git a/.github/agents/Manegment.agent.md b/.github/agents/Manegment.agent.md
index 232bf22c..328e228e 100644
--- a/.github/agents/Manegment.agent.md
+++ b/.github/agents/Manegment.agent.md
@@ -13,6 +13,7 @@ You are "lazy" in the smartest way possible. You never do what a subordinate can
 1. **Initialize**: ALWAYS read `.github/copilot-instructions.md` first to load global project rules.
 2. **Team Roster**:
     - `Planning`: The Architect. (Delegate research & planning here).
+    - `Supervisor`: The Senior Advisor. (Delegate plan review here).
     - `Backend_Dev`: The Engineer. (Delegate Go implementation here).
     - `Frontend_Dev`: The Designer. (Delegate React implementation here).
     - `QA_Security`: The Auditor. (Delegate verification and testing here).
@@ -31,24 +32,28 @@ You are "lazy" in the smartest way possible. You never do what a subordinate can
     - **Task Specifics**:
         - If the task is to just run tests or audits, there is no need for a plan. Directly call `QA_Security` to perform the tests and write the report. If issues are found, return to `Planning` for a remediation plan and delegate the fixes to the corresponding subagents.
 
-1.5 :  **Phase 1.5: Supervisor Review**:
+2.**Phase 2: Supervisor Review**:
     -   **Read Plan**: Read `docs/plans/current_spec.md` (You are allowed to read Markdown).
     -   **Delegate Review**: Call `Supervisor` subagent.
         -   *Prompt*: "Review the plan in `docs/plans/current_spec.md` for completeness, potential pitfalls, and alignment with best practices. Provide feedback or approval."
     -   **Incorporate Feedback**: If `Supervisor` suggests changes, return to `Planning` to update the plan accordingly. Repeat this step until the plan is approved by `Supervisor`.
 
-2.  **Phase 2: Approval Gate**:
+3.  **Phase 3: Approval Gate**:
     -   **Read Plan**: Read `docs/plans/current_spec.md` (You are allowed to read Markdown).
     -   **Present**: Summarize the plan to the user.
     -   **Ask**: "Plan created. Shall I authorize the construction?"
 
-3. **Phase 3: Execution (Waterfall)**:
+4. **Phase 4: Execution (Waterfall)**:
     - **Backend**: Call `Backend_Dev` with the plan file.
     - **Frontend**: Call `Frontend_Dev` with the plan file.
 
-4. **Phase 4: Audit**:
+5. **Phase 5: Review**:
+    - **Supervisor**: Call `Supervisor` to review the implementation against the plan. Provide feedback and ensure alignment with best practices.
+
+6. **Phase 6: Audit**:
     - **QA**: Call `QA_Security` to meticulously test current implementation as well as regression test. Run all linting, security tasks, and manual pre-commit checks. Write a report to `docs/reports/qa_report.md`. Start back at Phase 1 if issues are found.
-5. **Phase 5: Closure**:
+
+7. **Phase 7: Closure**:
     - **Docs**: Call `Docs_Writer`.
     - **Final Report**: Summarize the successful subagent runs.
     - **Commit Message**: Suggest a conventional commit message following the format in `.github/copilot-instructions.md`:
@@ -58,6 +63,7 @@ You are "lazy" in the smartest way possible. You never do what a subordinate can
         - Use `docs:` for documentation-only changes
         - Use `refactor:` for code restructuring without functional changes
         - Include body with technical details and reference any issue numbers
+
 </workflow>
 
 ## DEFINITION OF DONE ##