openspec-bulk-archive-change

Archives multiple completed OpenSpec changes with conflict-aware spec synchronization.

1|Updated Apr 9, 2026
One-click install
npx skills add https://github.com/CoderCoco-Studios/Hyveon --skill openspec-bulk-archive-change-codercoco-studios
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-bulk-archive-change
Source: https://github.com/CoderCoco-Studios/Hyveon/tree/main/.claude/skills/openspec-bulk-archive-change
Command: npx skills add https://github.com/CoderCoco-Studios/Hyveon --skill openspec-bulk-archive-change-codercoco-studios

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 specs. This Skill batches the entire archive workflow, detects spec conflicts, and resolves them by checking what is actually implemented in the codebase. ## Core Features & Use Cases - Batch archiving: Lists all active changes, prompts for multi-select, and archives the confirmed set in one operation with date-prefixed archive targets. - 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. - Verified spec sync: Runs the openspec-sync-specs workflow inline for included deltas and verifies main specs before moving any change directory. - Use Case: After finishing three parallel feature changes, ask the assistant to bulk-archive them; it shows a status table, resolves an auth spec conflict between two changes, and archives everything with a consolidated summary. ## Quick Start Ask the assistant to bulk archive all completed OpenSpec changes and confirm the selection 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, shows a consolidated status table, and archives the confirmed set after a single confirmation.

How are spec conflicts resolved when archiving changes?

The workflow maps each capability to the changes touching 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, sync is skipped with a warning.

Does bulk archive require the openspec CLI?

Yes, the workflow depends on the openspec CLI for listing changes, reading status and instructions, and validating artifacts. It also supports registered stores by passing the --store flag to commands that read or write specs and changes.

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

Incomplete changes appear with warnings in the status table. At confirmation you can archive everything, archive only ready changes and skip the incomplete ones, or cancel the entire batch so nothing is archived.

Can bulk archive fail partway through the batch?

Individual archive failures, such as an existing archive target, fail only that change while others continue. However, a failed specs-rule instruction lookup stops the whole batch atomically before any main-spec write or change move.