/implement_plan

Implement an approved technical plan from thoughts/shared/plans/. The agent follows the plan phase-by-phase, verifying success criteria at each step.

Usage

/implement_plan thoughts/shared/plans/2026-03-08-my-feature.md

Process

1. Read the plan — Reads the full plan and checks for existing progress (checkboxes)
2. Read referenced files — Reads the original ticket and all files mentioned in the plan
3. Create a todo list — Tracks progress through each phase
4. Implement each phase — Makes the specified changes
5. Verify — Checks success criteria after each phase
6. Update the plan — Marks checkboxes as phases are completed

Key Behavior

• Follows the plan’s intent — Adapts to what it finds while staying true to the plan’s goals
• Phase-by-phase — Completes each phase fully before moving to the next
• Communicates deviations — When reality doesn’t match the plan, explains why and what it did instead
• Updates checkboxes — Marks - [x] in the plan file as sections are completed

What This Adds

By default, AI tools implement things their own way. Even if you wrote a plan in a previous message, the model may silently diverge from it as it encounters unexpected code. /implement_plan takes a plan file path and follows the spec — it reads the plan, reads all referenced files, implements phase by phase, verifies success criteria after each phase, and checks off completed sections in the plan file. When it deviates, it communicates why rather than silently going its own way.

This creates an auditable trail: the plan file shows exactly which phases were completed and which remain.