What problem does it solve? Executing a multi-phase technical plan by hand is error-prone: steps get skipped, progress state gets lost between sessions, and commits end up mixing unrelated changes. This Skill drives plan execution deterministically from a canonical Progress section, keeping implementation state, commits, and change metadata consistent. ## Core Features & Use Cases - Progress-driven execution: Reads the ## Progress section of context/changes/<change-id>/plan.md as the single source of truth, resuming from the first unchecked item. - Phase-end commit ritual: Enforces manual verification gates, explicit path staging, dirty-path detection, Conventional Commits messages, and SHA write-back into completed Progress rows. - Mismatch handling: Pauses with a structured decision prompt when reality diverges from the plan instead of silently improvising. - Use Case: After approving a plan for an OAuth login change, run the Skill with the change-id to implement each phase, verify success criteria, and produce one clean commit per phase with traceable SHAs. ## Quick Start Ask the assistant to implement the approved plan for a change by running /10x-implement with your change-id, for example "implement the oauth-login plan starting at phase 1".
