openspec-bulk-archive-change

Archive multiple completed openspec changes in one batch with conflict-aware spec syncing.

Updated Mar 13, 2026
One-click install
npx skills add https://github.com/twaananen/6dof-drone-sim --skill openspec-bulk-archive-change-twaananen
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-bulk-archive-change
Source: https://github.com/twaananen/6dof-drone-sim/tree/main/.agents/skills/openspec-bulk-archive-change
Command: npx skills add https://github.com/twaananen/6dof-drone-sim --skill openspec-bulk-archive-change-twaananen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Archiving completed openspec changes one at a time is repetitive, and archiving several parallel changes risks spec conflicts when multiple changes touch the same capability. This Skill batches the entire operation and resolves conflicts by checking what is actually implemented in the codebase. ## Core Features & Use Cases - Batch archiving: Select and archive multiple active changes in a single confirmed operation, with per-change status tracking. - Conflict detection and resolution: Detects when 2+ changes modify the same capability spec, inspects the codebase for implementation evidence, and applies delta specs in the correct order. - Consolidated status reporting: Shows a summary table of artifacts, tasks, delta specs, and conflicts before asking for one batch confirmation. - Use Case: After finishing a sprint with five parallel openspec changes, run this Skill to review readiness, resolve an auth spec conflict between two changes, and archive everything with dated archive folders. ## Quick Start Ask the AI 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 via openspec list --json, lets you multi-select the ones to archive, shows a consolidated status table, and archives all confirmed changes into dated folders under openspec/changes/archive.

How are openspec spec conflicts resolved when archiving?▼

The workflow maps each capability to the changes touching it, then reads the conflicting 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.

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

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

Does bulk archive require the openspec CLI?▼

Yes, the workflow depends on the openspec CLI for listing changes and retrieving artifact status via openspec list --json and openspec status --change. Without the CLI installed, the batch status gathering steps cannot run.

What happens if the archive directory already exists?▼

That specific change fails with an error like 'Archive directory already exists', but the batch continues processing the remaining changes. The final summary reports successes, skips, and failures separately.