openspec-bulk-archive-change

Archives multiple completed OpenSpec changes in one batch with conflict detection.

Updated Apr 7, 2026
One-click install
npx skills add https://github.com/zh-impact/agent-feeder --skill openspec-bulk-archive-change-zh-impact
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-bulk-archive-change
Source: https://github.com/zh-impact/agent-feeder/tree/main/.claude/skills/openspec-bulk-archive-change
Command: npx skills add https://github.com/zh-impact/agent-feeder --skill openspec-bulk-archive-change-zh-impact

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Archiving many completed OpenSpec changes one at a time is repetitive, and overlapping delta specs can silently conflict when merged into the main specs. This Skill batch-archives selected changes while detecting and resolving spec conflicts by inspecting the actual codebase. ## Core Features & Use Cases - Batch archiving: Select and archive multiple active changes in a single confirmed operation, moving each to openspec/changes/archive/YYYY-MM-DD-<name>. - Conflict detection and resolution: Maps capabilities to the changes that touch them, then checks the codebase to decide which delta specs to sync and in what order. - Consolidated status reporting: Shows per-change artifact, task, and spec status in one table before confirmation, with warnings for incomplete work. - Use Case: After finishing several parallel feature changes (e.g., OAuth, JWT, and config updates), archive them all at once while ensuring the shared auth spec is merged in chronological order based on what is actually implemented. ## Quick Start Ask the assistant to bulk archive your completed OpenSpec changes and it will list active changes, let you pick which ones to archive, resolve any spec conflicts, and move them into the archive directory.

Frequently Asked Questions about openspec-bulk-archive-change

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I archive multiple OpenSpec changes at once?▼

Run the bulk archive workflow, which lists all active changes via `openspec list --json` and prompts you to multi-select which ones to archive. Each confirmed change is moved to `openspec/changes/archive/YYYY-MM-DD-<name>` after its delta specs are synced.

How are spec conflicts resolved when archiving changes?▼

The workflow builds a map of capabilities to the changes that touch them, then searches the codebase for implementation evidence. If only one change is implemented, its specs sync alone; if both are implemented, they apply in chronological order with the newer change taking precedence.

Does bulk archiving require the openspec CLI?▼

Yes, the workflow depends on the openspec CLI for listing active changes and retrieving artifact status via `openspec status --change <name> --json`. Without the CLI installed, change discovery and status gathering cannot run.

Can I archive a change with incomplete tasks?▼

Yes, but the workflow warns you first. The consolidated status table shows incomplete artifacts and unfinished tasks, and the confirmation step lets you archive only ready changes or proceed with warnings for incomplete ones.

What happens if the archive target directory already exists?▼

That specific change fails with an error while the remaining changes continue archiving. The final summary reports each outcome separately as archived, skipped, or failed so no failure silently blocks the batch.