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 mix unrelated changes. This Skill turns an approved plan.md into a disciplined, resumable implementation run with per-phase verification and clean Conventional-Commits history. ## Core Features & Use Cases - Phase-driven execution: Reads context/changes/<change-id>/plan.md, derives the next pending step from the canonical ## Progress section, and implements one phase at a time. - Verified phase-end commits: Runs automated success criteria, gates on manual confirmation, stages only touched files, and writes the closing commit SHA back into each completed Progress row. - Resumable state tracking: Progress lives only in the plan file — no sidecar state — so work can resume mid-plan or after a context reset using a generated resume command. - Use Case: After approving a plan for an OAuth login feature, run the Skill with the change-id to implement Phase 1, verify it, commit it with a Linear issue reference, and continue phase-by-phase until the change is marked implemented. ## Quick Start Ask the AI to implement the approved plan for your change by running /10x-implement with your change-id, for example the oauth-login change, and confirm each phase's manual verification as prompted.
