Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →hashgraph-online/release-archivist
Close out a spec-superflow change with verification, summary, and archive readiness.
Passed 11 of 17 test cases with the skill, and 6 of 17 without it.
and 5 more in the full report
8 fixed6 passed either way6 still failing2 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 8 test cases the skill fixed. Same model, same prompt, with and without the skill.
During active code implementation for `changes/user-auth`, the API structure was altered, causing a conflict with the original spec. What spec-superflow command transitions the change to bridging state so specs can be updated before continuing execution?
| Checked | Without skill | With skill |
|---|---|---|
| Executes `ssf state transition changes/user-auth bridging` to transition state to bridging | Missed | Passed |
The instructions your model reads when the skill loads.
Finish a spec-superflow change cleanly with verification evidence. This skill
operates while the change state is executing; it is not an active skill after
the final transition to closing.
Before verification, ssf audit, any DP state write, or delta-spec merge, run
ssf state get <change-dir> state.
Continue only when the persisted state is exactly executing. If it is
closing → STOP: "Closing is terminal; release, audit, and archival work were
completed before this transition." For any other state, or if the state cannot
be read → STOP and route through workflow-start; do not perform side effects.
For Quick, Tweak, or a valid direct incident Hotfix receipt, skip the Full verification, audit, delta merge, DP-6, and DP-7 sections below. Record changed files, the focused verification command and result, then persist test_result: pass and transition to closing. Quick requires a targeted test or syntax/static check; direct Hotfix requires an original-symptom regression. A legacy Hotfix stays on the Full checklist.
The Full checklist below applies only to Full and legacy Hotfix. Direct Short-Path Closure above takes precedence for Quick, Tweak, and valid direct Hotfix.
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 |
test cases passed, vs 6 / 17 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.