openspec-bulk-archive-change

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

Updated Feb 16, 2026
One-click install
npx skills add https://github.com/GQAdonis/artifact-refiner-skill --skill openspec-bulk-archive-change-gqadonis
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-bulk-archive-change
Source: https://github.com/GQAdonis/artifact-refiner-skill/tree/main/.kimi-code/skills/openspec-bulk-archive-change
Command: npx skills add https://github.com/GQAdonis/artifact-refiner-skill --skill openspec-bulk-archive-change-gqadonis

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Archiving many completed OpenSpec changes one at a time is slow and error-prone, especially when parallel changes touch the same capability specs. This Skill batches the archive operation, detects spec conflicts between changes, and resolves them by checking what is actually implemented in the codebase. ## Core Features & Use Cases - Batch archiving: Select and archive multiple active changes in one confirmed operation, with per-change status tracking for success, skip, and failure outcomes. - Conflict detection and resolution: Identifies when two or more changes modify the same capability spec path, inspects the codebase for implementation evidence, and applies delta specs in chronological order when both are implemented. - Spec sync verification: Syncs included delta specs into main specs and verifies ADDED, MODIFIED, REMOVED, and RENAMED requirements before moving any change into the archive directory. - Use Case: After finishing a sprint with five parallel feature changes, run the batch archive to review a consolidated status table, resolve a conflict on the identity/user-auth spec, and archive all ready changes with date-prefixed directory names. ## Quick Start Ask the assistant to archive all completed OpenSpec changes in this repository and confirm the batch when shown the status table.

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, prompts you to multi-select the ones to archive, shows a consolidated status table, and asks for a single confirmation before archiving the batch.

How are spec conflicts resolved when archiving parallel changes?

The workflow detects when two or more changes have delta specs for the same capability path, then 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.

Does the bulk archive require the openspec CLI?

Yes, the workflow depends on the openspec CLI for listing changes, reading status and artifact paths, and fetching instruction snapshots. It also supports registered stores via the --store flag for 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.

Why would a delta spec be skipped during archiving?

A delta spec is excluded from sync when no implementation evidence is found in the codebase for its requirements. The change can still be archived, but the excluded delta is reported as sync skipped with the recorded reason.