openspec-bulk-archive-change

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

Updated Jan 31, 2026
One-click install
npx skills add https://github.com/thewoolleyman/personal-knowledge-base --skill openspec-bulk-archive-change-thewoolleyman
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-bulk-archive-change
Source: https://github.com/thewoolleyman/personal-knowledge-base/tree/main/.claude/skills/openspec-bulk-archive-change
Command: npx skills add https://github.com/thewoolleyman/personal-knowledge-base --skill openspec-bulk-archive-change-thewoolleyman

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Archiving completed OpenSpec changes one at a time is tedious, and archiving several parallel changes 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 operation, moving them to dated archive directories. - Conflict Detection & Resolution: Detects when 2+ changes modify the same capability spec, inspects the codebase for implementation evidence, and applies specs in chronological order when both are implemented. - Status Reporting: Shows a consolidated table of artifact status, task completion, delta specs, and conflicts before confirming the batch operation. - 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 all completed work in one confirmed step. ## Quick Start Ask the assistant 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, prompts you to select changes, validates their status, and moves each to openspec/changes/archive/YYYY-MM-DD-<name> after syncing delta specs.

How are spec conflicts resolved when archiving parallel changes?▼

Conflicts occur when 2+ selected changes have delta specs for the same capability. The workflow reads each delta spec, searches the codebase for implementation evidence, and applies specs chronologically if both are implemented, or syncs only the implemented one.

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 all with warnings, or cancel the batch.

Does bulk archive require the openspec CLI?▼

Yes, the workflow requires the openspec CLI to list active changes and retrieve artifact status via openspec list --json and openspec status --change <name> --json. It also reads tasks.md and delta spec files directly from the openspec/changes directory.

What happens if the archive target directory already exists?▼

If the archive target YYYY-MM-DD-<name> already exists, that specific change fails with an error while the remaining changes continue processing. The final summary reports successes, skips, and failures separately.