zokmi Solo Release
This is the Solo SDD semantic closure gate. It does not own Git merge, pull request, branch, or worktree mechanics; leave those to finishing-a-development-branch.
Preconditions
Require fresh evidence from verification-before-completion, using the repository's actual format, lint, typecheck, test, and build commands as applicable. Do not infer success from code review or partial checks.
Closure Gate
Compare the final implementation and verification evidence with the approved scope:
- every material requirement and acceptance criterion is satisfied;
- every planned task is complete or explicitly removed through an approved scope change;
- no orphan implementation or speculative infrastructure remains;
- expected edge cases and failure paths have evidence;
- no unresolved TODO, placeholder, unexplained warning, or known regression contradicts completion.
For Spec Kit work, preserve semantic traceability:
requirement -> acceptance criterion -> implementation -> verification
For work that did not require Spec Kit, compare against the approved Superpowers design and plan instead.
Documentation Drift
Check the final behavior against durable documentation:
- architecture changed -> update architecture documentation;
- public behavior or contract changed -> update the specification and user-facing documentation;
- an important long-lived or difficult-to-reverse decision was made -> create or update an ADR when the repository uses ADRs;
- the implementation differs from an approved artifact -> reconcile and reapprove it before closure.
Result
- Closed: report the fresh verification evidence and the artifacts checked, then invoke
finishing-a-development-branch. - Open: list each unmet criterion or drift item and return it to the owning workflow. Do not merge, clean up, or label the change complete.