openspec-bulk-archive-change

Archive multiple completed openspec changes in one batch operation with conflict resolution.

Updated Nov 7, 2023
One-click install
npx skills add https://github.com/lstellway/nixfiles --skill openspec-bulk-archive-change-lstellway
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-bulk-archive-change
Source: https://github.com/lstellway/nixfiles/tree/main/modules/home-manager/claude/skills/openspec-bulk-archive-change
Command: npx skills add https://github.com/lstellway/nixfiles --skill openspec-bulk-archive-change-lstellway

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Archiving completed openspec changes one at a time is tedious, and archiving several parallel changes at once risks spec conflicts when multiple changes touch the same capability. This Skill batch-archives changes while detecting and resolving spec 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, moving each to openspec/changes/archive/YYYY-MM-DD-<name>. - Conflict Detection & Resolution: Maps capabilities to the changes that touch them, then inspects the codebase to determine which delta specs to sync and in what chronological order. - Consolidated Status Reporting: Shows a per-change table of artifact status, task completion, delta specs, and conflicts before asking for a single batch confirmation. - Use Case: After finishing three parallel feature changes (OAuth, project config, schema management), run this Skill to review their readiness, resolve an auth spec conflict, and archive all three with one confirmation. ## Quick Start Ask the assistant to bulk archive all completed openspec changes and resolve any spec conflicts before confirming.

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, 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 `openspec/changes/archive/YYYY-MM-DD-<name>` after one confirmation.

How are spec conflicts resolved when archiving parallel changes?

The Skill 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; if neither is implemented, spec sync is skipped with a warning.

Does bulk archiving require the openspec CLI?

Yes, the openspec CLI is required. The Skill runs `openspec list --json` to enumerate active changes and `openspec status --change <name> --json` to gather artifact status for each selected change.

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

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

What happens if the archive target directory already exists?

That individual change fails with an error while the rest of the batch continues. The final summary reports archived, skipped, and failed changes separately so no outcome is lost.