implement-plan

The system loads a plan file from thoughts/shared/plans and processes each phase sequentially. It performs automated verification against explicit success criteria at every milestone before advancing to the next phase.

Phase-gated implementation executes changes in sequential stages, requiring explicit user confirmation before advancing. It performs per-phase changes, commits with descriptive messages, and generates phase-gate prompts to ensure progress is measured against defined success criteria.

To load and run a plan, reference the markdown file in thoughts/shared/plans following the YYYY-MM-DD-*.md naming convention. The system executes each phase with automated verification and generates milestone-driven commits with descriptive messages.

Yes, automated milestone verification is designed for projects with multi-phase features, structured rollout, and testing procedures. It ensures progress is explicitly measured against success criteria at each phase gate before advancing.

Yes, phase-by-phase execution supports milestone-driven commits with descriptive messages. This provides clear progress reporting by tying each commit to the specific phase changes and automated verification results.