Menu
Finalizes a completed execution: delivery receipt, version bump, changelog. Use when every wave has passed, or /archive. Not before verification is green.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Divergent idea generation — many candidate ideas across several frames with judgment deferred, then a clustered shortlist. Use to open a solution space wide, or /brainstorm. Not for developing one idea (ideate) or picking one (propose).
Develops ONE chosen direction into a shaped concept — the core idea, how it works, what it needs, the open questions. Use to deepen a single idea, or /ideate. Not for generating many (brainstorm) or deciding among them (propose).
Structures a presentation narrative — the story arc, a slide-by-slide outline, and speaker notes — from results or receipts. Use to shape a talk or deck, or /present. Not for prose reports (report) or rendering visuals (asset).
Converges to a recommended approach — the options, their tradeoffs against stated criteria, a pick, and the rationale (plus what would change the call). Use to decide among approaches, or /propose. Not for generating options (brainstorm) or deep-diving one (ideate).
Plans a throwaway proof-of-concept to answer ONE feasibility unknown — the question, the smallest build that answers it, the success signal, and the discard plan. Use to de-risk before committing, or /prototype. Not for the real build (executor) or deciding (propose).
Produces a REDTEAM-FINDINGS.md probing your OWN AI app for jailbreak/injection/exfil/tool-abuse susceptibility, each reproduced and paired with a hardening, after a blocking authorization+ownership check. Use to red-team an owned AI system defensively.
| name | archive |
| description | Finalizes a completed execution: delivery receipt, version bump, changelog. Use when every wave has passed, or /archive. Not before verification is green. |
A task is not complete until you run. You are the permanent record. You read every receipt produced this execution, compile the consolidated not-tested list, determine the version bump, and write the delivery receipt. Implied completion is prohibited (I10) — you make completion provable and auditable. You never delete; prior receipts remain untouched.
The version you bump is the product's — what the user is building — not the engine's. This is the
v7 fix for v6's four-identities mess: the engine has exactly one version (VERSION, bumped only by a
framework release); the product has its own, and archive operates on that.
Does: aggregate the session's receipts, compile not_tested verbatim, run the pre-archive sweep,
bump the product version per the domain's policy, append a changelog entry, write the delivery
receipt, maintain the receipt index. Does not: run waves (executor), verify wave output (verifier),
delete any receipt, or touch the engine VERSION.
| Situation | Reference |
|---|---|
| Optional post-archive hooks: drift scoring, sweep mode, dependency-graph refresh, shift trigger, ticket closure | references/archive-hooks.md |
| CHANGELOG append, VERSION bump, delivery-receipt write, index patch delegation | engine/shared/references/script-delegation-contract.md |
<workspace>/receipts/ written this session<workspace>/VERSION) — accessed by the delegation
script, not loaded into context<workspace>/intake.json → domain; library/domains/<domain>/domain.yaml → version_policyMaintain <workspace>/archive/receipt-index.json as a queryable audit record across executions
(schema in schemas/). Status transitions: PENDING (intake) → IN_PROGRESS (scope-frame receipt) →
PASS / FAIL / BLOCKED (archive writes the delivery receipt). The index is never deleted — FAIL entries
are audit evidence.
Read the index (create with index_version: 1, empty tasks[] if absent). Find or create the entry
for task_id (do not duplicate). Update receipts_by_module for everything written this session
(written → PASS, not-run → PENDING, N/A → SKIP). Write it back before Step 1.
Read every receipt this execution: intake, scopeframe, specify, decompose, guard-wave-, wave-, verification-wave-*, execution, plus any reviewer receipts. Any required receipt missing → FAIL: record which is absent in the delivery receipt's failure reason; do not compose a delivery receipt with a gap in the chain.
Read not_tested from every receipt. Aggregate into one list; deduplicate exact duplicates but
preserve distinct items even if similar. This appears verbatim in the delivery receipt — nothing
minimized, summarized away, or hidden. Delivery is not blocked by not-tested items; they become the
starting scope for the next related session.
Invoke verifier in pre-archive sweep mode (verifier/references/pre-archive-sweep.md):
completeness / correctness / coherence. Non-blocking — findings are WARN, recorded under
pre_archive_sweep; archive proceeds regardless.
Read the domain's version_policy:
<workspace>/VERSION.<workspace>/VERSION is
authoritative; bump it.Bump size derives from the highest change class across the session's receipts (BREAKING > ADDITIVE >
COSMETIC → major / minor / patch). Never touch the engine VERSION. When the product is
WabbleSpec (self-build), the product version is the engine version — that is a special case of this
rule, not an exception to it.
Delegate the CHANGELOG append (append-only; never modify existing entries) and the delivery-receipt
write. Provide the reasoning-dependent arguments: --summary (synthesize from wave receipts: what was
produced and why), --delta-class (highest across receipts), --files-delivered (union of
files_written), --waves-completed (PASS count), --not-tested (one per aggregated item). The
script handles file I/O without loading CHANGELOG/VERSION into context.
Run any applicable post-archive hooks (references/archive-hooks.md) — all optional, none block
archiving. Report to the user: product version bumped X → Y, N receipts aggregated, not-tested count
(name the items if any — they are actionable future scope), and the delivery-receipt path.
delivery-receipt (<workspace>/receipts/delivery-receipt-<timestamp>.json): base + receipts_aggregated,
not_tested_items (count), version_previous, version_new, version_bump_reason
(BREAKING|ADDITIVE|COSMETIC), version_target (native-manifest path or "workspace"), waves_completed,
all_waves_passed, pre_archive_sweep (the 3-dimension result). persistence: Spec-Anchored.
CHANGELOG.md — append-only, in the product space (or workspace for workspace-policy products). Never modify existing entries.
VERSION: stop — archive bumps the product version; the engine
version changes only on a framework release.version_policy: default to workspace and bump <workspace>/VERSION;
record the assumption.status: FAIL: archive is FAIL — execution did not complete; do not write a PASS
delivery receipt over a failed chain.Done when: every required receipt was gathered (no gaps), the not-tested list is compiled verbatim, the pre-archive sweep ran, the product version was bumped per policy, the changelog was appended, and the delivery receipt was written; the receipt index reflects the final status.
Not done if: the delivery receipt was composed with a missing wave receipt; the engine VERSION was bumped; any not-tested item was summarized away or hidden.
Next step: the task is complete. Surface the delivery receipt; on framework self-build with spec
artifacts changed, the shift trigger (references/archive-hooks.md) may run.