What problem does it solve? Executing an approved multi-phase technical plan by hand is error-prone: steps get skipped, progress state is lost between sessions, and commits mix unrelated changes. This Skill drives plan execution deterministically from the plan's ## Progress section, keeping state, commits, and status files consistent. ## Core Features & Use Cases - Progress-driven execution: Reads the canonical ## Progress section in context/changes/<change-id>/plan.md, resumes from the first unchecked step, and flips checkboxes as steps complete. - Phase-end commit ritual: Enforces manual verification gates, explicit path staging, dirty-path detection, Conventional Commits messages with issue refs, and SHA write-back into Progress rows. - Lifecycle bookkeeping: Updates change.md status (implementing → implemented), syncs roadmap items to in-progress, and runs an epilogue commit to close out the plan. - Use Case: After /10x-plan produces an approved plan for a new feature, run /10x-implement my-feature phase 1 to implement each phase with verified commits, then resume later sessions exactly where you left off. ## Quick Start Ask the AI to implement the approved plan for a change by running /10x-implement with your change-id, optionally specifying a phase number to start from.
