Preconditions
Run complete after implementation is finished, you have reviewed the result, and the exact documented Verify command has passed. When Verify is not configured, the fallback build and relevant test commands must pass.
Complete refuses to merge while any P0 or P1 finding in blueprint/context/findings.md is open or fixed. Close findings through an audit re-review, or waive one explicitly: accepted requires your decision and a recorded reason, invalid marks a finding the review got wrong. See The Findings Ledger.
Work closeout
Complete:
- Archives the active spec under
blueprint/history/features/,blueprint/history/fixes/, orblueprint/history/rollbacks/. - Appends resolved findings to that archive with work-item prefixed IDs (
12/F-03), carries unresolved entries forward in the ledger, and resets the ledger when empty. - Checks off a completed feature, or unchecks the target of a completed rollback while preserving its number.
- Resets
current-feature.mdto its empty stub. - Creates one conventional work-level commit, including
revert:for rollback work. - Requests explicit approval before squash-merging into the default branch.
- Deletes the finished feature, fix, or rollback branch after the merge.
For a rollback, complete preserves the original feature archive and adds a separate dated rollback record with the target commit, reason, dependency review, compatibility work, and verification evidence. History records both that the feature shipped and why it was later removed.
Push boundary
Merge approval does not approve a push. Complete asks separately before pushing the default branch to a remote.
Why archive the spec
The history records what was intended, which checks defined success, and how the work was divided. It is useful project context without retaining chat transcripts.