Menu
Dress-rehearse a change before archiving — validate strictly, walk the verification ledger, and name the hard archive gates.
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
Run the apply gate for a change and implement its tasks, obeying the gate's exit code.
Archive a completed change — validate, merge specs, verify, and fan blockers out.
Archive a batch of completed changes in dependency order, one cospec archive call at a time.
Resume a partially-built change and finish its remaining artifacts.
Investigate the codebase or a spec question without writing implementation code.
Author every remaining artifact on an already-scaffolded change in one pass, then validate.
| name | cospec-verify-change |
| description | Dress-rehearse a change before archiving — validate strictly, walk the verification ledger, and name the hard archive gates. |
| license | MIT |
| compatibility | Requires the cospec CLI (@aligned-team/cospec). |
| metadata | {"author":"cospec","generatedBy":"cospec@0.5.1","contentHash":"sha256:fa9c999614a012ae1f53397848ad434aa3dbac73f812702ddeb1b10f59fac069"} |
Dress-rehearse a change before archiving it. This workflow does not archive — it
runs cospec validate --strict, walks the verification ledger to observed
evidence, and names the hard gates /cospec-archive will enforce.
All work goes through cospec. Never call openspec directly, and never
hand-edit the bookkeeping under openspec/changes/.
If the user named one, use it. Otherwise run cospec list --json and pick, or
ask.
cospec validate <slug> --strict
Fix every ERROR and every WARNING it reports before continuing. This includes the archive-precondition checks (targets exist, no zero-op deltas, no ADDED collisions, scenarios are well-formed) — do not proceed to the ledger walk with a validation failure outstanding.
Read openspec/changes/<slug>/verification.md. For each row shaped
- [ ] N.M @layer (owner) probe -> result:
->, replacing the placeholder.[x] once the observed result is recorded.- [~] N.M @layer (owner) probe -> defer: <honest reason> instead.No bare - [ ] row may remain when this step is done. Do not edit the ledger to
invent evidence for a probe you did not actually run.
Read openspec/changes/<slug>/tasks.md. Every box must be [x]. If any are
not, finish the remaining work (or tell the user which are outstanding) before
moving on.
Tell the user /cospec-archive runs two hard gates, neither of which accepts
--force:
archive/verification-incomplete — fails if any ledger row is still a bare
- [ ].archive/scenario-preservation — fails if a spec delta would drop a scenario
the living spec already has.This workflow only checks these preconditions; it does not run the archive.
Tell the user the change is dress-rehearsed and the next step is
/cospec-archive.