openspec-bulk-archive-change

Archive multiple openspec changes with conflict detection and ordered spec syncing.

5|Updated Apr 29, 2026

Search Tags:#CLI automation #archive #batch processing #conflict resolution #task validation #openspec #spec sync

Ready to run

npx skills add https://github.com/breuerfelix/spurwechsel --skill openspec-bulk-archive-change-breuerfelix

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-bulk-archive-change
Source: https://github.com/breuerfelix/spurwechsel/tree/main/.opencode/skills/openspec-bulk-archive-change
Command: npx skills add https://github.com/breuerfelix/spurwechsel --skill openspec-bulk-archive-change-breuerfelix

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you archive many completed spec changes at once without losing track of what is actually implemented or accidentally syncing conflicting spec updates.

Core Features & Use Cases

Batch archive of completed changes: Archives multiple selected changes into a dated archive folder in one operation.
Intelligent conflict detection and resolution: Detects when multiple selected changes touch the same capability and then checks the codebase to decide what specs to sync and in what order.
Per-change validation and reporting: Collects artifact status, task completion, and delta spec requirements, then shows a consolidated status table and a clear success/partial-success summary.

Quick Start

Ask the openspec tooling to run openspec-bulk-archive-change to select the changes you want to archive and then confirm the batch operation after reviewing the consolidated status and conflict resolutions.

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 completed openspec changes at once?▼

To batch archive multiple completed openspec changes, you select the desired changes via a multi-select prompt and confirm the batch operation. The Skill moves them into a dated archive folder in a single operation after validating artifacts and tasks.

What happens when archived spec changes have overlapping capability conflicts?▼

When overlapping capability conflicts are detected during spec changes archiving, the tool checks the codebase implementation evidence to determine the correct order for spec syncing. This conflict-aware resolution prevents accidental overwrites of valid specifications.

Do I need the openspec CLI to batch archive completed spec changes?▼

Yes, you need openspec CLI access to run the bulk archive operation. The Skill relies on the CLI to validate delta specs, check task completion, and execute conflict-aware spec syncing based on codebase evidence.

How does batch spec validation work for parallel changes?▼

Batch spec validation for parallel changes works by collecting artifact status, task completion, and delta spec requirements for each selected change. It then displays a consolidated status table showing success or partial-success before archiving.

Can I resolve spec sync conflicts automatically when archiving changes?▼

Spec sync conflicts are resolved automatically by verifying implementation evidence in the codebase. The tool detects when multiple selected changes touch the same capability and determines the correct ordered syncing sequence to prevent conflicts.

What is the best way to archive completed spec changes without losing track of implementations?▼

The best way to archive completed spec changes without losing track is to use conflict-aware batch validation. This approach verifies artifacts, tasks, and delta specs while checking the codebase to ensure only implemented updates are synced.