Before implementation
current-feature.md must contain a real feature, fix, or rollback spec. Implement refuses to improvise from the placeholder because scope, proof, and exclusions would be undefined.
The step loop
For each unchecked build step, implement:
- Changes only what that step requires.
- Shows the diff and explains each changed file.
- Runs the documented Verify command when present, or the relevant build and test commands when it is absent.
- Iterates until the done-when is true.
- Marks the step complete after your approval.
- Offers an optional checkpoint commit.
Audit repairs
When the ledger at blueprint/context/findings.md holds an open P0 or P1 finding against the active work, implement appends a repair step to the spec (- [ ] Repair F-03 - title), builds it in the same reviewed loop, and marks the finding fixed. A repair never closes itself; a later audit pass re-reviews the repaired code before the finding clears. See The Findings Ledger.
Branch behavior
Features use a feature/ branch, fixes use a fix/ branch, and rollbacks use a
rollback/ branch. The completed work remains on that branch until /complete
handles archival and merge approval.
Rollback safeguard
For a Type: Rollback spec, implement verifies that the archived feature still
maps to the exact approved commit and parent. It applies only that commit’s
product diff in reverse with three-way conflict detection. Blueprint plans,
context, history, adapters, agent instructions, and prototypes are excluded.
Implement shows the staged reverse diff and stops if a protected path changed or a later dependency causes a conflict. It never substitutes a whole-commit revert, broad checkout, stash, or reset for the reviewed rollback plan.
Testing gate
If AGENTS.md declares a Verify command, implement runs that exact recipe as the final automated gate. It can use a focused test first for faster feedback, but it does not replace or weaken Verify.
When Verify is absent and AGENTS.md declares a test command, logic-bearing steps must include focused tests and the suite must pass. UI work uses build output and browser evidence instead of brittle component tests.
What it never does
Implement does not silently broaden scope, hide a failing check, merge, push, deploy, publish, or send anything. A rollback also cannot cascade into another completed feature without a new plan and approval.