openspec-bulk-archive-change

Archives multiple completed OpenSpec changes in one batch with conflict-aware spec syncing.

4|Updated May 13, 2026
One-click install
npx skills add https://github.com/RuixeWolf/modbus-simulator --skill openspec-bulk-archive-change-ruixewolf
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-bulk-archive-change
Source: https://github.com/RuixeWolf/modbus-simulator/tree/main/.opencode/skills/openspec-bulk-archive-change
Command: npx skills add https://github.com/RuixeWolf/modbus-simulator --skill openspec-bulk-archive-change-ruixewolf

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Archiving many completed OpenSpec changes one at a time is slow and error-prone, especially when several changes touch the same capability spec. This Skill batches the entire archive workflow, detects spec conflicts between changes, and resolves them by checking what is actually implemented in the codebase. ## Core Features & Use Cases - Batch archiving: Lists all active changes, lets the user multi-select, validates artifacts and task completion, and archives them in a single confirmed operation. - Conflict detection and resolution: Maps delta specs by capability path, detects when two or more changes touch the same spec, and resolves conflicts by searching the codebase for implementation evidence. - Verified spec sync: Syncs included delta specs into main specs, verifies ADDED/MODIFIED/REMOVED/RENAMED requirements before moving any change, and reports per-change outcomes. - Use Case: After finishing a sprint with five parallel OpenSpec changes, run this Skill to review a consolidated status table, resolve a conflict on the identity/user-auth spec, and archive all ready changes with date-prefixed folders. ## Quick Start Ask the assistant to bulk archive all completed OpenSpec changes and confirm which ones to include 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, prompts you to multi-select the ones to archive, validates their artifacts and tasks, and archives them after a single confirmation.

What happens when two OpenSpec changes modify the same spec?▼

The workflow detects the conflict by capability path, reads both delta specs, and searches the codebase for implementation evidence. If both are implemented it applies them chronologically; if only one is implemented it syncs that one; if neither is found it skips the sync with a warning.

Does bulk archive require the openspec CLI?▼

Yes, the workflow depends on the openspec CLI for listing changes, reading status JSON, fetching instructions, and validating artifacts. It also supports registered stores via the --store flag when the work lives in a standalone OpenSpec repo.

Can I archive a change with incomplete tasks?▼

Yes, but the status table flags it with warnings showing incomplete artifacts and tasks. During confirmation you can choose to archive everything, archive only ready changes, or cancel the entire batch.

What happens if spec sync verification fails during archiving?▼

The change is not archived and its changeRoot stays intact. The workflow reports which capability spec failed verification, records the failure, and continues processing the remaining confirmed changes.