What problem does it solve? Approved technical plans often drift during implementation: steps get skipped, progress tracking gets lost, and commits bundle unrelated changes. This Skill executes a plan from context/changes/<change-id>/plan.md phase by phase, keeping the plan's Progress section as the single source of truth and producing one clean Conventional-Commits commit per phase. ## Core Features & Use Cases - Phase-driven execution: Resolves a change-id or plan path, reads the plan and referenced files fully, creates one task per phase, and resumes from the first unchecked Progress item. - Structured verification ritual: Runs success criteria, gates on manual confirmation, stages only touched files by explicit path, detects unrelated dirty paths, and writes the commit SHA back into each completed Progress row. - Mismatch handling: When reality diverges from the plan, it presents the discrepancy and asks whether to adapt, skip, or re-plan instead of silently improvising. - Use Case: After approving a three-phase plan for adding OAuth login, run the skill with the change-id to implement each phase, verify it, and land a scoped commit like feat(oauth-login): add token endpoint (p1) with the SHA recorded in the plan. ## Quick Start Ask the assistant to implement the approved plan for your change-id, for example by saying: implement the plan at context/changes/oauth-login/plan.md starting with phase 1.
