openspec-bulk-archive
Archive multiple completed changes at once with /opsx:bulk-archive, handling spec conflicts between changes. Use when the user says "archive all changes", "bulk archive", "/opsx:bulk-archive", or has multiple completed changes.
- Installs
- 102
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/full-stack-skills/openspec-skills --skill openspec-bulk-archive- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads openspec-bulk-archive automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
OpenSpec Bulk Archive Skill
Use /opsx:bulk-archive to archive multiple completed changes at once. Validates each change, detects spec conflicts across changes, and resolves them by checking what is actually implemented.
When to Use
- Multiple changes are completed and ready to archive.
- The user says "archive all", "bulk archive", "clean up finished changes".
- After a sprint or batch of parallel work.
Prerequisites
- Multiple active changes with completed tasks.
Workflow
-
Run bulk archive
/opsx:bulk-archive— lists all completed changes and prompts to select./opsx:bulk-archive <name1> <name2> ...— archive specific changes.
-
What happens
- Lists all completed changes.
- Validates each change before archiving.
- Detects spec conflicts across changes (e.g. two changes touch the same spec file).
- Resolves conflicts by checking what is actually implemented in the codebase.
- Archives in chronological order (by creation date).
-
Confirm
- The agent shows the list and conflict resolution plan; the user confirms.
Outputs
- All selected changes archived to
openspec/changes/archive/. - Delta specs merged into
openspec/specs/in chronological order.
Next Steps
- Start new changes with openspec-new.
Troubleshooting
- Spec conflicts: The agent inspects the codebase to resolve; review the resolution before confirming.
- Incomplete changes: Bulk archive warns about incomplete tasks but does not block.
References
FAQ
What does the openspec-bulk-archive skill do?
Archive multiple completed changes at once with /opsx:bulk-archive, handling spec conflicts between changes. Use when the user says "archive all changes", "bulk archive", "/opsx:bulk-archive", or has multiple completed changes.
How do I install openspec-bulk-archive?
Run npx skills add https://github.com/full-stack-skills/openspec-skills --skill openspec-bulk-archive in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/openspec-bulk-archive/ (personal) or .claude/skills/openspec-bulk-archive/ (project).
Which AI agents can use openspec-bulk-archive?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is openspec-bulk-archive safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains openspec-bulk-archive?
It is published by full-stack-skills in full-stack-skills/openspec-skills. It has 102 recorded installs.
More from full-stack-skills/openspec-skills
openspec-apply
full-stack-skills/openspec-skills
Implement tasks from the change using /opsx:apply, working through the task list and checking off items. Use when the user says "implement", "apply the change", "/opsx:apply", or "start coding from tasks".
openspec-new
full-stack-skills/openspec-skills
Start a new OpenSpec change with /opsx:new, creating a change folder with metadata and scaffolding. Use when the user says "start a new change", "new feature", "/opsx:new", or "create an OpenSpec change".
openspec-update
full-stack-skills/openspec-skills
Run openspec update to regenerate AI tool instruction files after upgrading the OpenSpec CLI. Use when the user says "update OpenSpec", "openspec update", or "refresh OpenSpec skills/commands".
openspec-initial
full-stack-skills/openspec-skills
Run openspec init to initialize OpenSpec in a project directory, creating the openspec/ folder structure and configuring AI tool integrations. Use when the user says "initialize OpenSpec", "openspec init", or "set up OpenSpec in this project".
openspec-install
full-stack-skills/openspec-skills
Install the OpenSpec CLI globally via npm, pnpm, yarn, bun, or nix. Use when the user says "install OpenSpec", "set up OpenSpec", or "openspec command not found".
openspec-archive
full-stack-skills/openspec-skills
Archive a completed change with /opsx:archive, merging delta specs into main specs and preserving the change for history. Use when the user says "archive the change", "finish up", "/opsx:archive", or "mark this change as done".
Popular code quality & workflow skills
grill-me
mattpocock/skills
A relentless interview to sharpen a plan or design.
improve-codebase-architecture
mattpocock/skills
Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.
handoff
mattpocock/skills
Compact the current conversation into a handoff document for another agent to pick up.
domain-modeling
mattpocock/skills
Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.
codebase-design
mattpocock/skills
Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.
diagnosing-bugs
mattpocock/skills
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.