openspec-bulk-archive-change

Archive multiple completed OpenSpec changes while resolving delta-spec conflicts.

Updated Jun 4, 2025

Search Tags:#workflow #codebase #archive #openspec #bulk #delta-specs

Ready to run

npx skills add https://github.com/alexei-lexx/budget --skill openspec-bulk-archive-change-alexei-lexx

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-bulk-archive-change
Source: https://github.com/alexei-lexx/budget/tree/main/.gemini/skills/openspec-bulk-archive-change
Command: npx skills add https://github.com/alexei-lexx/budget --skill openspec-bulk-archive-change-alexei-lexx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archive multiple completed OpenSpec changes in a single operation, reducing manual overhead and ensuring consistent archival history.

Core Features & Use Cases

Batch archiving: Archive several completed changes in one operation.
Conflict-aware: Detects delta-spec conflicts and resolves them by inspecting the codebase to determine implementation coverage.
Safe archival: Archives changes to archive/YYYY-MM-DD-<name> and preserves original configuration files for traceability.
Use Case: When you finish a sprint with several OpenSpec changes, run the bulk archive to consolidate them without duplicating work.

Quick Start

Run the bulk-archive operation after selecting which changes to archive.

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?▼

You can bulk-archive multiple completed OpenSpec changes in a single operation by scanning active changes, selecting which ones to archive, and moving them to the archive directory while preserving original configuration files.

What happens to delta-spec conflicts during a bulk OpenSpec archive?▼

When delta-spec conflicts are detected during the archive process, the tool resolves them by inspecting the codebase to determine implementation coverage before safely archiving each change.

Do I need the OpenSpec CLI to batch-archive completed codebase changes?▼

Yes, the OpenSpec CLI is required to perform a safe bulk archive. The tool reads per-change status, tasks, and specs directly through the CLI to ensure accurate archival.

How are archived OpenSpec changes stored and organized?▼

Archived changes are stored in a structured archive directory using the format archive/YYYY-MM-DD-<name>. Original .openspec.yaml configuration files are preserved within each archive for traceability.

When should I run a bulk archive for my OpenSpec workflow?▼

You should run a bulk archive after finishing a sprint or development cycle with several completed OpenSpec changes. This consolidates archival history and reduces manual overhead without duplicating work.

Can I choose which specific OpenSpec changes to include in a batch archive?▼

Yes, the bulk archive operation scans all active changes and prompts you to select specifically which completed changes you want to archive, ensuring you maintain full control over the archival process.