القائمة
Close out a spec-superflow change with verification, summary, and archive readiness. Invoke when implementation is complete, verification is underway, or the user asks for a final wrap-up.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Review completed implementation batches for spec compliance and code quality. Invoke after execution batches complete, before merging, or when a review gate is reached in the workflow.
Govern implementation from an approved execution contract. Invoke when execution-contract.md is approved and the user wants disciplined build work, TDD execution, or guarded batch-by-batch implementation.
Primary entry point for the spec-superflow state-machine workflow. Invoke when the user is inside an active spec-superflow change directory (look for .spec-superflow.yaml, changes/<name>/, proposal.md, specs/, design.md, tasks.md, or execution-contract.md) and asks to start, continue, resume, implement, plan, or figure out the next workflow step. Also invoke when the user explicitly asks to start a new spec-superflow change or route through the spec-superflow workflow. Do not invoke for unrelated coding tasks that happen to use words like start, continue, implement, or plan.
Convert approved planning artifacts into an execution contract. Invoke when the user wants to start building, asks to move from planning to implementation, or when execution-contract.md is missing or stale.
Use when encountering any bug, test failure, or unexpected behavior during spec-superflow execution, before proposing fixes. Invoked automatically when build-executor hits a blockage.
Clarify intent, scope, constraints, and success criteria before artifact creation. Invoke when the request is fuzzy, the user is comparing options, or the workflow needs a stable change definition before writing artifacts.
| name | release-archivist |
| description | Close out a spec-superflow change with verification, summary, and archive readiness. Invoke when implementation is complete, verification is underway, or the user asks for a final wrap-up. |
Finish a spec-superflow change cleanly with verification evidence.
Claiming work is complete without verification is dishonesty, not efficiency. Before claiming any status:
Forbidden before evidence: "should", "probably", "seems to", expressions of satisfaction without output.
| Claim | Requires | Not Sufficient |
|---|---|---|
| Tests pass | Test output: 0 failures | Previous run, "should pass" |
| Linter clean | Linter output: 0 errors | Partial check |
| Build succeeds | Build exit 0 | Linter passing |
| Bug fixed | Original symptom passes | Code changed |
| Requirements met | Line-by-line checklist | Tests passing |
Run full test suite. Record total/passed/failed/skipped. Zero failures = PASS.
Compare contract batches against actual diff. Every SHALL/MUST must have implementation evidence. Missing = Critical severity.
Compare design decisions against code. Check naming consistency. Inconsistencies = IMPORTANT.
Check for files modified outside scope fence, new dependencies not in design. Unplanned = WARN.
| Dimension | Status | Findings |
|---|---|---|
| Completeness | PASS/FAIL/WARN | [list] |
| Correctness | PASS/FAIL/WARN | [list] |
| Coherence | PASS/FAIL/WARN | [list] |
Verdict: PASS (all PASS) / CONDITIONAL (WARN only) / FAIL (any FAIL).
node "${CLAUDE_PLUGIN_ROOT}/scripts/spec-superflow.mjs" audit <change-dir> — include decision-point-audit.md in archivenode "${CLAUDE_PLUGIN_ROOT}/scripts/spec-superflow.mjs" state set <change-dir> dp_6_result "<pass|conditional|fail>: <summary>"
node "${CLAUDE_PLUGIN_ROOT}/scripts/spec-superflow.mjs" state set <change-dir> dp_6_timestamp $(date -u +%Y-%m-%dT%H:%M:%SZ)
If FAIL, do NOT proceed to DP-7. Route back or ask about abandonment.
After recording a PASS outcome, also record it as the verification gate so the
executing → closing transition is allowed (the guard accepts either
test_result: pass or a dp_6_result starting with pass):
node "${CLAUDE_PLUGIN_ROOT}/scripts/spec-superflow.mjs" state set <change-dir> test_result pass
node "${CLAUDE_PLUGIN_ROOT}/scripts/spec-superflow.mjs" state set <change-dir> dp_7_result "confirmed: <archive summary>"
node "${CLAUDE_PLUGIN_ROOT}/scripts/spec-superflow.mjs" state set <change-dir> dp_7_timestamp $(date -u +%Y-%m-%dT%H:%M:%SZ)
Verify DP-0 through DP-6 are recorded before DP-7.
If implementation diverged from the contract, return to bridging before closure.
Run node "${CLAUDE_PLUGIN_ROOT}/scripts/spec-superflow.mjs" state transition <change-dir> closing. If delta specs exist, route to spec-merger.
Verify files exist and are non-empty, run node --check on code files, skip 5-step verification. Still record DP-6 and DP-7.
node "${CLAUDE_PLUGIN_ROOT}/scripts/spec-superflow.mjs" audit manually