01
It starts by itself
end of sprint. Runs in Claude Code routine.
- ↻ end of sprint
0 16 * * 5
fission-ai · 4K installsOpenSpec Bulk Archive Change skill
Runs by itself, end of sprint.
Clear finished changes in batches.
Install the OpenSpec Bulk Archive Change skill and make it a habit: follow https://gethabit.dev/skills/fission-ai/openspec-bulk-archive-change.md
- 1Copy
- 2Paste into Claude Code, Codex or Cursor
- 3It runs by itself
4K installs73K starsMIT licenceSource on GitHub ↗
OpenSpec Bulk Archive Change
by fission-ai · 4K installs
The skill
The openspec bulk archive change skill archives several finished OpenSpec changes at once, resolving spec conflicts by checking the codebase and asking one confirmation, for teams running parallel spec work.
Only when you ask.
The habit
Clear finished changes in batches.
↻ Runs by itselfend of sprint
How the habit works.
You don't have to.
When does it start? How does it check its work? What does it remember?
One run, step by step.
Then it stops.
Stops after one batch per run.
- 01
List changes
Run openspec list --json and stop if no active changes exist.
- 02
You select
Ask you to pick changes; never pick them on your own.
- 03
Validate batch
Run openspec status --change with --json for each and check task counts and archive targets.
- 04
Find conflicts
Map delta specs by capability path and flag paths touched by two or more changes.
- 05
Resolve conflicts
Search the codebase for implementation evidence and decide which deltas to sync.
- 06
Confirm once
Show a status table and ask one batch question.
- 07
Sync and archive
Run openspec-sync-specs inline for included deltas, verify, then move each change.
- 08
Summarize
Report archived, skipped and failed changes plus sync results.
What it may do.
Nothing more.
It writes only in its own folder and asks you before anything goes out.
- Writes only inopenspec/**
- Talks tono outside service
- Sendsnothing
- Your OKIt asks you before anything goes out.
Is it for you?
Use it when it fits.
Read both lists. If the left one sounds like you, the OpenSpec Bulk Archive Change skill helps.
Use it when
- ✓ Several changes are finished
- ✓ Changes touch the same spec
- ✓ You say openspec archive all
Skip it when
- – Only one change is done
- – Changes are still in progress
OpenSpec Bulk Archive Change skill, answered.
What if two changes edit the same spec?
The agent checks the code. If both are built, it applies them oldest first.
What if an archive folder already exists?
That change fails and is left in place, and the rest of the batch continues.
How do I install the OpenSpec Bulk Archive Change skill?
Copy the prompt at the top into your agent. It installs the skill from fission-ai/openspec and sets up the habit. Or run npx skills add fission-ai/openspec --skill openspec-bulk-archive-change.
Is the OpenSpec Bulk Archive Change skill free?
Yes. It is published under MIT. Habit is free too.
OpenSpec Bulk Archive Change. Now as a habit.
Install the OpenSpec Bulk Archive Change skill and make it a habit: follow https://gethabit.dev/skills/fission-ai/openspec-bulk-archive-change.md
All fission-ai skills →More docs skills →
Works in
- Claude Code
- Codex
- Cursor
- ChatGPT
- Claude app
Made by fission-ai, published under MIT. Habit links to the original and never changes it. Is this your skill?