openspec-bulk-archive-change
Archive multiple completed OpenSpec changes at once
by fission-aiFree
Description
openspec-bulk-archive-change is an agent skill from the OpenSpec project for archiving several completed changes in one operation. It is meant for the case where several parallel changes are finished and you want them closed out together, and it also handles a plural request such as archiving all the completed changes. Its main feature is how it handles spec conflicts. When two changes touch the same specification, the skill checks the codebase to work out what is actually implemented, so that it does not archive a change on the strength of a spec that another change has already overwritten or that was never built. The skill follows the same safety checks as the other OpenSpec workflows: it confirms the project has an OpenSpec root before the first write, and it stops rather than creating an openspec folder when the project is not set up. It also handles store selection, and when a store is in use it keeps the store id for the whole batch. It is for developers and maintainers who finish a batch of work across several branches and want the changes archived without going through each one. Install it with npx skills add https://github.com/fission-ai/openspec --skill openspec-bulk-archive-change.…
Highlights
- Archives several completed changes in one operation
- Checks the codebase to resolve spec conflicts
- Confirms the project root before any write
- Keeps the store id for the whole batch
Ratings & Reviews
No ratings yet
Be the first to rate openspec-bulk-archive-change.
People also visit
openspec-continue-change
Continue working on an OpenSpec change by creating the next artifact
openspec-propose
Propose a new OpenSpec change with all artifacts generated in one step
openspec-update-change
Update an OpenSpec change by revising its existing planning artifacts
verify-openspec-docs
Fact-checks OpenSpec user documentation with a fresh-context subagent
openspec-bulk-archive-change FAQ
When is bulk archive the right choice?
When you have several parallel changes that are finished and want them archived together.
How does it handle conflicting specs?
It checks the codebase to determine what is actually implemented, instead of trusting the spec files alone.
Does it need an OpenSpec project?
Yes. It confirms an OpenSpec root first and stops rather than creating one.
How do I install it?
Run npx skills add https://github.com/fission-ai/openspec --skill openspec-bulk-archive-change.
What are the best openspec-bulk-archive-change alternatives?
Popular alternatives to openspec-bulk-archive-change include draft-openspec-docs, openspec-continue-change and openspec-ff-change. See all openspec-bulk-archive-change alternatives