10x-implement

You can track technical plan progress by executing phase-specific requirements, updating per-row checkmarks in the plan's Progress section, and staging only touched files to commit with a Conventional-Commits message. The resulting commit SHA is then written back to the flipped rows.

Executing a technical plan phase-by-phase requires running success criteria checks, pausing for manual verification, and advancing from the first pending checkbox. If reality diverges from the plan, the workflow stops to ask whether to adapt, skip, or re-plan.

To resume an interrupted implementation plan, the workflow uses existing checked marks in the plan's authoritative Progress section as the source of truth. It reads the current state, validates the plan path, and continues from the next pending phase.

Yes, it supports monorepo workflows by staging only the touched files at the end of each phase. It refuses archived changes under context/archive and ensures strict mutation of only the Progress section during the implementation work.

Implementation stops when reality diverges from the plan to prevent untracked changes. The workflow detects the mismatch, explains the issue, and asks the user whether to adapt the current code, skip the phase, or re-plan the technical approach entirely.

Yes, you can run 10x-implement with just a change-id. It resolves and validates the plan path automatically, reads the Progress section, and advances implementation starting from the first pending checkbox without requiring an explicit phase number.