do

Phased subagent orchestration executes a multi-phase implementation plan by delegating implementation, verification, and code quality review to dedicated subagents. Each subagent completes checklist steps and provides evidence before the orchestrator advances to the next phase.

Evidence-based completion requires each subagent to provide commands run, outputs, and files changed before advancing. This verification process ensures that implementation steps are validated against actual results rather than assumptions, preventing unverified code from progressing.

Guardrails against assumptions prevent inventing APIs or undocumented parameters by verifying against documentation and stopping when uncertainty is found. This ensures implementation is anchored to verified documentation throughout the execution workflow.

No, commit gating ensures code is committed only after verification, anti-pattern detection, and code quality review pass. This phased approach preserves checklist order and requires evidence-based completion across phases and branches before any commit occurs.

Coordinating specialized subagents for plan-driven development requires running discrete phases for implementation, verification, anti-pattern checks, and code quality review. Fresh subagents are spawned per phase when needed, ensuring each step matches the plan through evidence collection.

No, this Skill requires a repository change plan created by a planner as input. It carries out the implementation by executing the phased plan, coordinating subagents to complete each checklist step and verify results before committing.