openspec-bulk-archive-change

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

5|Updated Mar 21, 2026
One-click install
npx skills add https://github.com/8007342/tillandsias --skill openspec-bulk-archive-change-8007342
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-bulk-archive-change
Source: https://github.com/8007342/tillandsias/tree/main/.opencode/skills/openspec-bulk-archive-change
Command: npx skills add https://github.com/8007342/tillandsias --skill openspec-bulk-archive-change-8007342

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 spec. 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: Maps delta specs by capability path, detects when two or more changes touch the same spec, and resolves conflicts by searching the codebase for implementation evidence. - Verified spec sync: Runs the openspec-sync-specs workflow inline for included deltas and verifies main specs before moving any change into the archive directory. - Use Case: After finishing a sprint with five parallel changes, two of which both modify the identity/user-auth spec, run this Skill to review a consolidated status table, resolve the conflict chronologically, and archive everything in one confirmation. ## Quick Start Ask the assistant to bulk archive all completed OpenSpec changes and resolve any spec conflicts before moving them to the archive folder.

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 multi-select changes, shows a consolidated status table, and archives the confirmed set in one operation with a single confirmation.

How are spec conflicts resolved when two changes touch the same capability?▼

The workflow maps delta specs by capability path and flags conflicts when two or more changes target the same path. It searches the codebase for implementation evidence, then syncs only implemented changes, applying both in chronological order when both exist.

Does bulk archive work with OpenSpec stores?▼

Yes. When a store is named, the workflow runs openspec store list --json to discover registered store ids and passes --store <id> on all commands that read or write specs and changes, keeping the flag sticky for the rest of the workflow.

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

Incomplete changes appear with warnings in the status table showing artifact and task counts. You can choose to archive everything, archive only ready changes, or cancel; skipped changes are recorded and reported in the final summary.

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 change name, capability path, and reason.