openspec-bulk-archive-change

Archives multiple completed OpenSpec changes in one batch with spec conflict resolution.

Updated Apr 6, 2026
One-click install
npx skills add https://github.com/capella-hotel-group/capella-hotel-group-poc --skill openspec-bulk-archive-change-capella-hotel-group
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-bulk-archive-change
Source: https://github.com/capella-hotel-group/capella-hotel-group-poc/tree/main/.github/skills/openspec-bulk-archive-change
Command: npx skills add https://github.com/capella-hotel-group/capella-hotel-group-poc --skill openspec-bulk-archive-change-capella-hotel-group

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Archiving many completed OpenSpec changes one at a time is repetitive and error-prone, especially when several changes touch the same capability specs. This Skill batch-archives selected changes while detecting and resolving spec conflicts by inspecting the actual codebase. ## Core Features & Use Cases - Batch archiving: Lists active changes via the openspec CLI, prompts for multi-select, and moves each confirmed change into a dated archive directory. - Conflict detection and resolution: Maps capabilities to the changes that modify them, then checks the codebase to decide which delta specs to sync and in what order. - Status reporting: Shows a consolidated table of artifacts, tasks, specs, and conflicts before a single confirmation, then reports success, skip, and failure outcomes. - Use Case: After finishing three parallel feature changes (OAuth, project config, schema management), archive them all at once while automatically resolving that two of them both modified the auth spec. ## Quick Start Ask the assistant to bulk archive all completed OpenSpec changes and resolve any spec conflicts before archiving.

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 active changes with openspec list, prompts you to multi-select the ones to archive, then moves each into openspec/changes/archive with a YYYY-MM-DD prefix after a single confirmation.

How are spec conflicts resolved when archiving changes?▼

The workflow 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 taking precedence.

Does bulk archive require the openspec CLI?▼

Yes, the workflow depends on the openspec CLI for listing active changes and retrieving per-change artifact status in JSON format. Without the CLI installed, the status gathering and validation steps cannot run.

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

Incomplete changes are flagged in the status table with warnings showing unfinished artifacts and tasks. You can choose to archive only the ready changes and skip incomplete ones, or archive everything with warnings.

What happens if the archive directory already exists?▼

If the dated archive target already exists, that specific change fails with an error while the remaining changes continue archiving. The final summary reports each failure separately alongside successful archives.