release-archivist

Name: release-archivist
Author: MageByte-Zero

24installs58forks

How to install release-archivist?

magebyte-zero/spec-superflow/release-archivist

$npx -y skills add MageByte-Zero/spec-superflow --skill release-archivist

Installs into the current project.

Summary

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.

Files · 1

View on GitHub

SKILL.md

1	# Release Archivist
2
3	Finish a spec-superflow change cleanly with verification evidence. This skill
4	operates while the change state is `executing`; it is not an active skill after
5	the final transition to `closing`.
6
7	## Execution-State Guard
8
9	Before verification, `ssf audit`, any DP state write, or delta-spec merge, run
10	`npx --yes --package spec-superflow@0.11.0 ssf state get <change-dir> state`.
11	Continue only when the persisted state is exactly `executing`. If it is
12	`closing` → STOP: "Closing is terminal; release, audit, and archival work were
13	completed before this transition." For any other state, or if the state cannot
14	be read → STOP and route through `workflow-start`; do not perform side effects.
15
16	## The Iron Law: Verification Before Completion
17
18	Claiming work is complete without verification is dishonesty, not efficiency. Before claiming any status:
19	1. IDENTIFY the command that proves the claim
20	2. RUN the full command fresh
21	3. READ output, check exit code
22	4. VERIFY output confirms the claim
23	5. Only THEN make the claim
24
25	Forbidden before evidence: "should", "probably", "seems to", expressions of satisfaction without output.
26
27	\| Claim \| Requires \| Not Sufficient \|
28	\|-------\|----------\|----------------\|
29	\| Tests pass \| Test output: 0 failures \| Previous run, "should pass" \|
30	\| Linter clean \| Linter output: 0 errors \| Partial check \|
31	\| Build succeeds \| Build exit 0 \| Linter passing \|
32	\| Bug fixed \| Original symptom passes \| Code changed \|
33	\| Requirements met \| Line-by-line checklist \| Tests passing \|
34
35	## Verification Steps
36
37	### Step 1: Test Suite
38	Run full test suite. Record total/passed/failed/skipped. Zero failures = PASS.
39
40	### Step 2: Completeness
41	Compare contract batches against actual diff. Every SHALL/MUST must have implementation evidence. Missing = Critical severity.
42
43	### Step 3: Coherence
44	Compare design decisions against code. Check naming consistency. Inconsistencies = IMPORTANT.
45
46	### Step 4: Unintended Scope
47	Check for files modified outside scope fence, new dependencies not in design. Unplanned = WARN.
48
49	### Step 5: Report
50
51	\| Dimension \| Status \| Findings \|
52	\|-----------\|--------\|----------\|
53	\| Completeness \| PASS/FAIL/WARN \| [list] \|
54	\| Correctness \| PASS/FAIL/WARN \| [list] \|
55	\| Coherence \| PASS/FAIL/WARN \| [list] \|
56
57	Verdict: PASS (all PASS) / CONDITIONAL (WARN only) / FAIL (any FAIL).
58	- FAIL → fix issues or route back to build-executor
59	- CONDITIONAL → present WARNs, proceed only with user acceptance
60	- PASS → proceed to final checks
61
62	## Final Checks
63
64	- Tests passing? (cite command and output)
65	- All batches complete? (cite batch status)
66	- Scope added without artifact updates?
67	- Unresolved blockers or known risks?
68	- Delta specs exist that need merging?
69	- Run `npx --yes --package spec-superflow@0.11.0 ssf audit <change-dir>` — include `decision-point-audit.md` in archive
70
71	### DP-6 (Verification Outcome)
72	```bash
73	npx --yes --package spec-superflow@0.11.0 ssf state set <change-dir> dp_6_result "<pass\|conditional\|fail>: <summary>"
74	npx --yes --package spec-superflow@0.11.0 ssf state set <change-dir> dp_6_timestamp $(date -u +%Y-%m-%dT%H:%M:%SZ)
75	```
76	If FAIL, do NOT proceed to DP-7. Route back or ask about abandonment.
77
78	After recording a PASS outcome, also record it as the verification gate so the
79	`executing → closing` transition is allowed (the guard accepts either
80	`test_result: pass` or a `dp_6_result` starting with `pass`):
81	```bash
82	npx --yes --package spec-superflow@0.11.0 ssf state set <change-dir> test_result pass
83	```
84
85	### DP-7 (Archive Confirmation)
86	```bash
87	npx --yes --package spec-superflow@0.11.0 ssf state set <change-dir> dp_7_result "confirmed: <archive summary>"
88	npx --yes --package spec-superflow@0.11.0 ssf state set <change-dir> dp_7_timestamp $(date -u +%Y-%m-%dT%H:%M:%SZ)
89	```
90	Verify DP-0 through DP-6 are recorded before DP-7.
91
92	## Archive Rule
93
94	If implementation diverged from the contract, return to `bridging` before closure.
95
96	## Finalize While Executing
97
98	Complete every release, delta-spec synchronization, and audit action while the
99	state remains `executing`. If delta specs exist, invoke `spec-merger` and
100	resolve its outcome before the final `executing → closing` transition. Then
101	run `npx --yes --package spec-superflow@0.11.0 ssf state transition <change-dir> closing`.
102	`executing → closing` is the final action: once it succeeds, select no next
103	skill and run no recovery scans.
104
105	## Lightweight Closure (hotfix/tweak)
106
107	Verify files exist and are non-empty, run `node --check` on code files, skip 5-step verification. Still record DP-6 and DP-7.
108
109	## Exception Handling
110
111	- Parse failures: Report exact file and section
112	- Missing files: If audit can't generate, run `npx --yes --package spec-superflow@0.11.0 ssf audit` manually
113	- User interruption: Re-run verification

People who liked this also viewed

6 picks

Type

release-archivist

24installs58forks

View on GitHub

How to install release-archivist?

magebyte-zero/spec-superflow/release-archivist

$npx -y skills add MageByte-Zero/spec-superflow --skill release-archivist

Installs into the current project.

Summary

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.

Files · 1

View on GitHub

SKILL.md

1	# Release Archivist
2
3	Finish a spec-superflow change cleanly with verification evidence. This skill
4	operates while the change state is `executing`; it is not an active skill after
5	the final transition to `closing`.
6
7	## Execution-State Guard
8
9	Before verification, `ssf audit`, any DP state write, or delta-spec merge, run
10	`npx --yes --package spec-superflow@0.11.0 ssf state get <change-dir> state`.
11	Continue only when the persisted state is exactly `executing`. If it is
12	`closing` → STOP: "Closing is terminal; release, audit, and archival work were
13	completed before this transition." For any other state, or if the state cannot
14	be read → STOP and route through `workflow-start`; do not perform side effects.
15
16	## The Iron Law: Verification Before Completion
17
18	Claiming work is complete without verification is dishonesty, not efficiency. Before claiming any status:
19	1. IDENTIFY the command that proves the claim
20	2. RUN the full command fresh
21	3. READ output, check exit code
22	4. VERIFY output confirms the claim
23	5. Only THEN make the claim
24
25	Forbidden before evidence: "should", "probably", "seems to", expressions of satisfaction without output.
26
27	\| Claim \| Requires \| Not Sufficient \|
28	\|-------\|----------\|----------------\|
29	\| Tests pass \| Test output: 0 failures \| Previous run, "should pass" \|
30	\| Linter clean \| Linter output: 0 errors \| Partial check \|
31	\| Build succeeds \| Build exit 0 \| Linter passing \|
32	\| Bug fixed \| Original symptom passes \| Code changed \|
33	\| Requirements met \| Line-by-line checklist \| Tests passing \|
34
35	## Verification Steps
36
37	### Step 1: Test Suite
38	Run full test suite. Record total/passed/failed/skipped. Zero failures = PASS.
39
40	### Step 2: Completeness
41	Compare contract batches against actual diff. Every SHALL/MUST must have implementation evidence. Missing = Critical severity.
42
43	### Step 3: Coherence
44	Compare design decisions against code. Check naming consistency. Inconsistencies = IMPORTANT.
45
46	### Step 4: Unintended Scope
47	Check for files modified outside scope fence, new dependencies not in design. Unplanned = WARN.
48
49	### Step 5: Report
50
51	\| Dimension \| Status \| Findings \|
52	\|-----------\|--------\|----------\|
53	\| Completeness \| PASS/FAIL/WARN \| [list] \|
54	\| Correctness \| PASS/FAIL/WARN \| [list] \|
55	\| Coherence \| PASS/FAIL/WARN \| [list] \|
56
57	Verdict: PASS (all PASS) / CONDITIONAL (WARN only) / FAIL (any FAIL).
58	- FAIL → fix issues or route back to build-executor
59	- CONDITIONAL → present WARNs, proceed only with user acceptance
60	- PASS → proceed to final checks
61
62	## Final Checks
63
64	- Tests passing? (cite command and output)
65	- All batches complete? (cite batch status)
66	- Scope added without artifact updates?
67	- Unresolved blockers or known risks?
68	- Delta specs exist that need merging?
69	- Run `npx --yes --package spec-superflow@0.11.0 ssf audit <change-dir>` — include `decision-point-audit.md` in archive
70
71	### DP-6 (Verification Outcome)
72	```bash
73	npx --yes --package spec-superflow@0.11.0 ssf state set <change-dir> dp_6_result "<pass\|conditional\|fail>: <summary>"
74	npx --yes --package spec-superflow@0.11.0 ssf state set <change-dir> dp_6_timestamp $(date -u +%Y-%m-%dT%H:%M:%SZ)
75	```
76	If FAIL, do NOT proceed to DP-7. Route back or ask about abandonment.
77
78	After recording a PASS outcome, also record it as the verification gate so the
79	`executing → closing` transition is allowed (the guard accepts either
80	`test_result: pass` or a `dp_6_result` starting with `pass`):
81	```bash
82	npx --yes --package spec-superflow@0.11.0 ssf state set <change-dir> test_result pass
83	```
84
85	### DP-7 (Archive Confirmation)
86	```bash
87	npx --yes --package spec-superflow@0.11.0 ssf state set <change-dir> dp_7_result "confirmed: <archive summary>"
88	npx --yes --package spec-superflow@0.11.0 ssf state set <change-dir> dp_7_timestamp $(date -u +%Y-%m-%dT%H:%M:%SZ)
89	```
90	Verify DP-0 through DP-6 are recorded before DP-7.
91
92	## Archive Rule
93
94	If implementation diverged from the contract, return to `bridging` before closure.
95
96	## Finalize While Executing
97
98	Complete every release, delta-spec synchronization, and audit action while the
99	state remains `executing`. If delta specs exist, invoke `spec-merger` and
100	resolve its outcome before the final `executing → closing` transition. Then
101	run `npx --yes --package spec-superflow@0.11.0 ssf state transition <change-dir> closing`.
102	`executing → closing` is the final action: once it succeeds, select no next
103	skill and run no recovery scans.
104
105	## Lightweight Closure (hotfix/tweak)
106
107	Verify files exist and are non-empty, run `node --check` on code files, skip 5-step verification. Still record DP-6 and DP-7.
108
109	## Exception Handling
110
111	- Parse failures: Report exact file and section
112	- Missing files: If audit can't generate, run `npx --yes --package spec-superflow@0.11.0 ssf audit` manually
113	- User interruption: Re-run verification

People who liked this also viewed

6 picks

Type