openspec-bulk-archive-change

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Archiving several completed openspec changes one by one is repetitive and error-prone, especially when multiple changes touch the same capability specs. This Skill batches the full archive protocol, detects spec conflicts across changes, and resolves them by checking what is actually implemented in the codebase. ## Core Features & Use Cases - Batch archiving with full protocol: Runs the complete per-change archive protocol (slice-gate, verify report, marker balance, code-truth, ADR/KB extraction) for every selected change, never skipping gates because of bulk mode. - Spec 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. - Consolidated status and summary: Shows a per-change status table (artifacts, tasks, specs, conflicts) before a single batch confirmation, then reports archived, skipped, and failed outcomes. - Use Case: After finishing three parallel changes (oauth, project-config, schema-management), select all of them, let the Skill resolve the shared auth spec conflict by checking the code, and archive everything in one confirmed operation. ## Quick Start Ask the assistant to bulk archive all completed openspec changes and select the ones you want from the multi-select prompt.

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: it lists active changes via openspec list, lets you multi-select which ones to archive, validates each one, and executes the full archive protocol per change with a single batch confirmation.

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

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

Does bulk archive skip the normal archive checks?

No. Each change still goes through the full single-archive protocol: slice-gate on unaccepted slices, verify report freshness, marker balance, code-truth checks, and ADR/KB extraction. Changes that fail a gate are skipped with a reason in the summary.

What happens if one change fails during bulk archiving?

The failing change is recorded as failed with its error (for example, archive target directory already exists), and the batch continues with the remaining changes. The final summary lists archived, skipped, and failed changes separately.

Can I archive an incomplete change in bulk mode?

The status table flags incomplete artifacts or tasks before confirmation, and you can choose to archive only ready changes. Conscious bypass of the full protocol requires an explicit per-change force option, same as single archive.