openspec-bulk-archive-change

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

Updated Jul 23, 2026
One-click install
npx skills add https://github.com/shrek-abaper/sap-nexus-agent --skill openspec-bulk-archive-change-shrek-abaper
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-bulk-archive-change
Source: https://github.com/shrek-abaper/sap-nexus-agent/tree/main/.comet/skills/skills/openspec-bulk-archive-change
Command: npx skills add https://github.com/shrek-abaper/sap-nexus-agent --skill openspec-bulk-archive-change-shrek-abaper

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Archiving many completed OpenSpec changes one by one is repetitive and error-prone, especially when several changes touch the same capability specs. This Skill batch-archives selected changes, detects spec conflicts between them, and resolves conflicts by checking what is actually implemented in the codebase. ## Core Features & Use Cases - Batch archiving: Lists active changes via openspec list --json, lets the user multi-select changes, and archives them into openspec/changes/archive/YYYY-MM-DD-<name> in one confirmed operation. - Status validation: Gathers artifact status, task completion counts from tasks.md, and delta spec inventories for every selected change before archiving. - Conflict detection and resolution: Maps capabilities to the changes that touch them, then inspects the codebase to decide which delta specs to sync and in what chronological order. - Use Case: After finishing three parallel feature changes that both modify the auth spec, run this Skill to review a consolidated status table, confirm the batch, and archive all three with specs synced in the correct order. ## Quick Start Ask the assistant to bulk archive your completed OpenSpec changes and select the ones you want from the presented list.

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 flow, which lists active changes with `openspec list --json` and prompts you to multi-select the ones to archive. After a single confirmation, each selected change is moved to `openspec/changes/archive/YYYY-MM-DD-<name>`.

How are spec conflicts resolved when archiving parallel changes?▼

The skill maps each capability to the changes that touch it, then searches the codebase for implementation evidence. If only one change is implemented, its specs sync; if both are implemented, they apply in chronological order with the newer change taking precedence.

Does bulk archiving require the openspec CLI?▼

Yes, the openspec CLI is required. The skill runs `openspec list --json` and `openspec status --change <name> --json` to gather change and artifact status before archiving.

What happens if a change has incomplete tasks during bulk archive?▼

Incomplete changes are flagged in the consolidated status table with warnings showing unfinished artifacts and tasks. You can choose to archive only ready changes, archive all with warnings, or cancel the batch.

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 archived, skipped, and failed changes separately.