Archive a completed OpenSpec change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete. Also use when the user says "openspec archive" or "opsx archive".
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
Archive a completed change in the experimental workflow.
**Store selection:** If the user names a store (a store is a standalone OpenSpec repo registered on this machine) or the work lives in one, run `openspec store list --json` to discover registered store ids, then pass `--store <id>` on the commands that read or write specs and changes (`new change`, `status`, `instructions`, `list`, `show`, `validate`, `archive`, `doctor`, `context`, `schemas`, `view`). Once selected, treat `--store <id>` as sticky for the rest of the workflow. Every unscoped example of those commands below is shorthand: before running it, append the flag. For example, run `openspec status --change "<name>" --json --store "<id>"`, not the unscoped form shown below. Other commands do not take the flag. Hints printed by commands already carry the flag; keep it on follow-ups. Without a store, commands act on the nearest local `openspec/` root.
…
The line at the top of this page pins the label v1.0, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
GET https://markdownregistry.com/api/v1/artifacts/art_6tfuof5jrceztp5p
GET https://markdownregistry.com/api/v1/resolve?ref=intent-driven-dev/intent-driven-template/openspec-archive-change
GET https://markdownregistry.com/api/v1/blob/ca99f962f4786e294317d7036036d0900051a9fb08cbb2aee046d7f8c05e85f2
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
intent-driven-dev/intent-driven-template · .agents/skills/acceptance-test-authoring/SKILL.md · Use when creating or modifying acceptance tests, configuring cucumber-js or behave runners, writing or refactoring step…
intent-driven-dev/intent-driven-template · .agents/skills/c4-diagrams/SKILL.md · Use when explaining existing code architecture, visualizing a new system before detailed design, mapping software…
intent-driven-dev/intent-driven-template · .agents/skills/grill-me/SKILL.md · Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of…
intent-driven-dev/intent-driven-template · .agents/skills/openspec-git-discipline/SKILL.md · Use when running OpenSpec propose, continue, apply, verify, archive, or worktree workflows where proposal artifacts…
intent-driven-dev/intent-driven-template · .agents/skills/spec-as-source/SKILL.md · Use when a user or project explicitly adopts OpenSpec spec-as-source, fenced Gherkin specifications as executable…
intent-driven-dev/intent-driven-template · .agents/skills/test-driven-development/SKILL.md · Use when implementing a change with test-driven development (TDD): work test-first through focused red-green cycles.
intent-driven-dev/intent-driven-template · .opencode/skills/adversarial-authoring/SKILL.md · Use when rules or instructions mention "adversarial-authoring", "adversarial authoring", "must use…
intent-driven-dev/intent-driven-template · .opencode/skills/openspec-apply-change/SKILL.md · Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or…
intent-driven-dev/intent-driven-template · .opencode/skills/openspec-bulk-apply-change/SKILL.md · Use when multiple active OpenSpec changes should be applied concurrently in isolated worktrees with delegated…
monid-ai/monid · .opencode/skills/openspec-archive-change/SKILL.md · Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after…
fengshao1227/ccg-workflow · .agents/skills/openspec-archive-change/SKILL.md · Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after…
mememeow-studio/mememeow · .opencode/skills/openspec-archive-change/SKILL.md · Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after…
mememeow-studio/mememeow · .claude/skills/openspec-archive-change/SKILL.md · Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after…
mememeow-studio/mememeow · .agents/skills/openspec-archive-change/SKILL.md · Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after…
partcad/partcad · .cursor/skills/openspec-archive-change/SKILL.md · Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after…
partcad/partcad · .claude/skills/openspec-archive-change/SKILL.md · Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after…
asymmetric-al/core · .agents/skills/openspec-archive-change/SKILL.md · Archive a completed OpenSpec change in the experimental workflow. Use when the user wants to finalize and archive a…