openspec-bulk-archive-change

Archives multiple completed OpenSpec changes with conflict detection and spec synchronization.

Updated Jun 25, 2026
One-click install
npx skills add https://github.com/ismaelsoilet/ismaelsoilet-landing --skill openspec-bulk-archive-change-ismaelsoilet
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-bulk-archive-change
Source: https://github.com/ismaelsoilet/ismaelsoilet-landing/tree/main/.cursor/skills/openspec-bulk-archive-change
Command: npx skills add https://github.com/ismaelsoilet/ismaelsoilet-landing --skill openspec-bulk-archive-change-ismaelsoilet

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Archiving many completed OpenSpec changes one by one is slow and error-prone, especially when several changes touch the same capability specs. This Skill batches the entire archive workflow, detects spec conflicts between changes, and verifies that delta specs are actually implemented in the codebase before syncing them. ## Core Features & Use Cases - Batch archiving: Lists all active changes, lets the user multi-select which ones to archive, and moves them into the dated archive directory in one confirmed operation. - Conflict detection and resolution: Maps capabilities to the changes that modify them, then inspects the codebase to decide which delta specs to sync, in chronological order when both are implemented. - Verified spec sync: Runs the openspec-sync-specs workflow inline and verifies ADDED, MODIFIED, REMOVED, and RENAMED requirements in the main specs before moving any change directory. - Use Case: After a sprint with five parallel changes, two of which both modify the auth spec, run this Skill to review a consolidated status table, resolve the auth conflict based on actual code, and archive everything with a single confirmation. ## Quick Start Ask the assistant to bulk archive all completed OpenSpec changes and confirm the selection when prompted.

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. After a single confirmation, it syncs delta specs and moves each change into the dated archive directory.

How are spec conflicts resolved when two changes touch the same capability?▼

The workflow reads each change's delta specs and searches the codebase for implementation evidence. If only one change is implemented, only its specs sync; if both are implemented, they apply in chronological order with the newer change taking precedence.

Does bulk archive work with OpenSpec stores?▼

Yes. If the work lives in a registered store, the workflow runs openspec store list --json to discover store ids and passes --store <id> to all commands that read or write specs and changes. Without a store, commands act on the nearest local openspec root.

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

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

Why would a delta spec be skipped during archiving?▼

A delta spec is skipped when no implementation evidence is found in the codebase for its requirements. The change can still be archived, but the skipped sync is reported separately with the change, capability, and reason.