openspec-archive-change is agent-read markdown (skill) from muthuishere/toolnexus: Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
Archive a completed change in the experimental workflow.
**Input**: Optionally specify a change name. If omitted, check if it can be inferred from conversation context. If vague or ambiguous you MUST prompt for available changes.
**Steps**
1. **If no change name provided, prompt for selection**
Run `openspec list --json` to get available changes. Use the **AskUserQuestion tool** to let the user select.
Show only active changes (not already archived).
Include the schema used for each change if available.
**IMPORTANT**: Do NOT guess or auto-select a change. Always let the user choose.
2. **Check artifact completion status**
Run `openspec status --change "<name>" --json` to check artifact completion.
Parse the JSON to understand:
- `schemaName`: The workflow being used
- `planningHome`, `changeRoot`, `artifactPaths`, and `actionContext`: path and scope context
- `artifacts`: List of artifacts with their status (`done` or other)
If status reports `actionContext.mode: "workspace-planning"`, explain that workspace archive is not supported in this slice and STOP. Do not move workspace changes into repo-local archives or edit linked repos.
…
Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
GET https://markdownregistry.com/api/v1/artifacts/art_d2z2goryzdqu7cwh
GET https://markdownregistry.com/api/v1/resolve?ref=muthuishere/toolnexus/openspec-archive-change
GET https://markdownregistry.com/api/v1/blob/0526054ec891a8a0c0cd0e19a285f285aa111112f2480a3ab365f9bba18a2b9c
Your agent 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.
muthuishere/toolnexus · .claude/skills/openspec-apply-change/SKILL.md · Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or…
muthuishere/toolnexus · .claude/skills/openspec-explore/SKILL.md · Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use…
muthuishere/toolnexus · .claude/skills/openspec-propose/SKILL.md · Propose a new change with all artifacts generated in one step. Use when the user wants to quickly describe what they…
muthuishere/toolnexus · .claude/skills/openspec-sync-specs/SKILL.md · Sync delta specs from a change to main specs. Use when the user wants to update main specs with changes from a delta…
muthuishere/toolnexus · .claude/skills/release/SKILL.md · Cut and verify a toolnexus release across all seven registries, with the guardrails that a green CI run does not give…
muthuishere/toolnexus · clojure/examples/clj-ex1/skills/clojure-events/SKILL.md · Use when asked about Clojure community events, meetups or conferences. How to fetch and report them.
muthuishere/toolnexus · clojure/examples/cljgo-ex1/skills/clojure-events/SKILL.md · Use when asked about Clojure community events, meetups or conferences. How to fetch and report them.
muthuishere/toolnexus · examples/skills/hello-world/SKILL.md · A tiny example skill. Use when you want to see how skill loading (progressive disclosure) works end to end.
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…
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…
intent-driven-dev/intent-driven-template · .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…
rustyrazorblade/skills · .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…
yazelin/ching-tech-os · .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…
yazelin/ching-tech-os · .github/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…
jim60105/copilot-prompt · 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…
