skills.rest
raphaelmans
raphaelmansCOMMUNITY
Explore all skills by this author →
GitHub

openspec-bulk-archive-change

Archive multiple completed OpenSpec changes in one batch with conflict-aware spec syncing.

Updated Sep 7, 2026
Search Tags:#cli#archive#conflict resolution#change management#batch#openspec#spec sync
One-click install
npx skills add https://github.com/raphaelmans/spectralpointengineering --skill openspec-bulk-archive-change-raphaelmans
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-bulk-archive-change
Source: https://github.com/raphaelmans/spectralpointengineering/tree/main/.skillshare/skills/openspec-bulk-archive-change
Command: npx skills add https://github.com/raphaelmans/spectralpointengineering --skill openspec-bulk-archive-change-raphaelmans

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Archiving many completed OpenSpec changes one at a time is repetitive and error-prone, especially when several changes touch the same capability spec. This Skill batches the entire archive workflow, 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 any number of active changes in a single confirmed operation, with per-change status tracking. - Conflict detection and resolution: Identifies when two or more changes modify the same capability spec path and resolves conflicts by searching the codebase for implementation evidence, applying specs in chronological order when both are implemented. - Verified spec sync: 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 changes, run the batch archive to review a consolidated status table, resolve an identity/user-auth spec conflict between two changes, and archive everything with one confirmation. ## 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 all active changes, prompts you to multi-select the ones to archive, shows a consolidated status table, and archives them after a single confirmation. Each change is moved to the archive directory with a YYYY-MM-DD prefixed name.

How are spec conflicts resolved when archiving parallel changes?▼

Conflicts are detected when two or more selected changes have delta specs for the same capability path. The workflow reads each delta spec, searches the codebase for implementation evidence, and syncs only implemented changes, applying both in chronological order when both are implemented.

Does the openspec CLI need to be installed for bulk archiving?▼

Yes, the openspec CLI is required. The workflow runs commands like openspec list, status, instructions, and archive with JSON output, and it supports registered stores via the --store flag for standalone OpenSpec repositories.

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

Incomplete changes are flagged in the status table with warnings showing unfinished artifacts and tasks. You can choose to archive everything, archive only ready changes, or cancel, and skipped or failed changes are reported separately in the final summary.

Can a change be archived if its spec sync fails verification?▼

No. After syncing included delta specs, the workflow verifies main specs for added, modified, removed, and renamed requirements. If verification fails, that change is not moved to the archive and the failure is reported, while other changes continue.

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
crozzbitecrozzbite

openspec-sync-specs

Merge delta specs into main specs using the openspec CLI.

Community
Advanced
zabinyzabiny
2

openspec-archive-change

Archive completed OpenSpec changes after validating artifacts, tasks, and delta-spec status.

Official
Advanced
agentxmagentxm
5

openspec-bulk-archive-change

Batch-archive completed OpenSpec changes with conflict resolution and configuration preservation.

Official
Advanced