openspec-bulk-archive-change from intent-driven-dev/intent-driven-template is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
Archive multiple completed OpenSpec changes at once. Use when archiving several parallel changes. Also use for a plural archive request - "openspec bulk-archive", "opsx bulk-archive", "openspec archive all", or "openspec archive these changes".
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 multiple completed changes in a single operation.
This skill allows you to batch-archive changes, handling spec conflicts intelligently by checking the codebase to determine what's actually implemented.
**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_ynnfu7o7bynrrxpq
GET https://markdownregistry.com/api/v1/resolve?ref=intent-driven-dev/intent-driven-template/openspec-bulk-archive-change
GET https://markdownregistry.com/api/v1/blob/064577aaedc2adaac454a42b9ef6c5e577eda4263503f81ed202166e4fb0ac6f
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-archive-change/SKILL.md · Archive a completed OpenSpec change in the experimental workflow. Use when the user wants to finalize and archive a…
fengshao1227/ccg-workflow · .agents/skills/openspec-bulk-archive-change/SKILL.md · Archive multiple completed changes at once. Use when archiving several parallel changes.
taskless/cli · .agents/skills/openspec-bulk-archive-change/SKILL.md · Archive multiple completed changes at once. Use when archiving several parallel changes.
rustyrazorblade/skills · .claude/skills/openspec-bulk-archive-change/SKILL.md · Archive multiple completed changes at once. Use when archiving several parallel changes.
yazelin/ching-tech-os · .github/skills/openspec-bulk-archive-change/SKILL.md · Archive multiple completed changes at once. Use when archiving several parallel changes.
yazelin/ching-tech-os · .claude/skills/openspec-bulk-archive-change/SKILL.md · Archive multiple completed changes at once. Use when archiving several parallel changes.
jim60105/copilot-prompt · skills/openspec-bulk-archive-change/SKILL.md · Archive multiple completed OpenSpec changes at once. Use when archiving several parallel changes. Also use for a plural…