What problem does it solve? Executing an approved technical plan by hand is error-prone: steps get skipped, progress state gets lost between sessions, and commits mix unrelated changes. This Skill drives plan execution phase by phase, keeping the plan's Progress section as the single source of truth and producing clean, auditable commits. ## Core Features & Use Cases - Phased plan execution: Reads context/changes/<change-id>/plan.md, finds the next pending step in the ## Progress section, and implements each phase fully before moving on. - State tracking and resume: Flips - [ ] to - [x] in the Progress section only, derives current position from the plan itself, and supports resuming mid-plan with no sidecar state files. - Phase-end commit ritual: Runs automated verification, gates on manual confirmation, stages only touched files by explicit path, proposes Conventional Commits messages with issue tracker Refs: lines, and writes the commit SHA back into completed Progress rows. - Use Case: After approving a plan for adding OAuth login, run the Skill with the change-id to implement phase 1, verify it, commit it with a traceable message, and continue or resume later with a copied resume command. ## Quick Start Ask the assistant to implement the approved plan for a change by running /10x-implement with your change-id, for example the oauth-login change, optionally specifying a phase number.
