What problem does it solve? Turning an approved spec into code often degrades into unreviewed, oversized changes that are hard to verify or undo. This Skill enforces a disciplined build loop: one small step at a time, each with a visible diff, a plain-English explanation, and test evidence before the user approves it. ## Core Features & Use Cases - Step-by-step implementation: Reads the spec in blueprint/context/current-feature.md and builds each step as the smallest change satisfying its done-when criteria, showing diffs rather than whole files. - Verification gates: Runs the project's declared Verify command or fallback build and tests before any commit, and checks off completed steps in the spec so progress survives a context reset. - Guarded rollback support: For Type: Rollback specs, applies a reverse patch of only the approved product diff while protecting Blueprint history paths, stopping on any conflict or drift. - Use Case: After running /feature to spec a new settings page, run /implement to create the feature branch, build each step with reviewed diffs and passing tests, then hand off to /complete for the merge. ## Quick Start Ask the assistant to run /implement to start building the current spec in blueprint/context/current-feature.md one reviewed step at a time.
