skills.rest
trutoman
trutomanCOMMUNITY
Explore all skills by this author →
GitHub

openspec-bulk-archive-change

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

1|Updated Jun 30, 2026
Search Tags:#cli#archive#batch operations#conflict resolution#change management#openspec#spec sync
One-click install
npx skills add https://github.com/trutoman/Conjuros --skill openspec-bulk-archive-change-trutoman
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-bulk-archive-change
Source: https://github.com/trutoman/Conjuros/tree/main/.opencode/skills/openspec-bulk-archive-change
Command: npx skills add https://github.com/trutoman/Conjuros --skill openspec-bulk-archive-change-trutoman

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Archiving many completed OpenSpec changes one at a time is slow and risky when several 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: Maps capabilities to the changes that modify 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 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 auth spec, run a single bulk archive that syncs only the implemented deltas and moves each change into the dated archive folder. ## Quick Start Ask the assistant to bulk archive my completed OpenSpec changes and resolve any spec conflicts before moving them.

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, prompts you to multi-select changes, validates their status, and archives them in one confirmed batch. Each change is moved to the archive directory with a YYYY-MM-DD prefixed name.

How are spec conflicts resolved when archiving parallel changes?▼

The workflow builds a map of capabilities to the changes touching them, 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 with the newer change taking precedence.

Does bulk archive work with OpenSpec stores?▼

Yes. When a store is named or the work lives in one, the workflow runs openspec store list to discover registered store ids and passes 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 in the status table with warnings showing unfinished artifacts and tasks. You can choose to archive everything, archive only ready changes, or cancel; skipped changes are recorded 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, capability, and reason.

Related Skills

Explore More Software Engineering Skills→
epamepam
503

openspec-archive-change

Validate and archive completed Openspec workflow changes while preserving configuration files.

Official
Advanced
jacobcyjacobcy
6

openspec-sync-specs

Merge delta spec changes into main specs while preserving unrelated content.

Community
Advanced
brandon-setegnbrandon-setegn

openspec-bulk-archive-change

Archive multiple OpenSpec changes after validating task completion and spec overlap.

Community
Advanced
open-platform-modelopen-platform-model

openspec-bulk-archive-change

Batch archive multiple completed OpenSpec changes with conflict detection and status validation.

Official
Advanced