What problem does it solve? It prevents unreviewed implementation plans from reaching execution by requiring a formal critic verdict, revision loops, and a recorded approval before any coder is dispatched. ## Core Features & Use Cases - Plan Critic Review: Delegates the full plan.md and codebase context to the swarm's critic agent and handles APPROVED, NEEDS_REVISION (max 2 cycles), and REJECTED verdicts. - Approval Verification & Escape Hatch: Confirms the recorded approval via get_approved_plan before dispatch, with an audited manual override (approve_plan_critic) when the mechanical recorder fails. - Spec Gates & Traceability: Enforces SPEC-GATE before save_plan, blocks tools on spec staleness drift, and requires every MUST/SHALL SC-### obligation to map to plan tasks. - Use Case: An architect agent writes .swarm/plan.md, runs CRITIC-GATE once, gets an APPROVED verdict recorded, and only then dispatches coders in MODE: EXECUTE without hitting PLAN_CRITIC_GATE_VIOLATION. ## Quick Start Ask the architect agent to run the critic-gate protocol on the newly written .swarm/plan.md before starting any implementation.