openspec-bulk-archive-change

Batch-archive completed OpenSpec changes with conflict-aware handling and date-stamped file moves.

84|18|Updated Feb 11, 2026
One-click install
npx skills add https://github.com/intent-driven-dev/openspec-schemas --skill openspec-bulk-archive-change-intent-driven-dev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-bulk-archive-change
Source: https://github.com/intent-driven-dev/openspec-schemas/tree/main/.opencode/skills/openspec-bulk-archive-change
Command: npx skills add https://github.com/intent-driven-dev/openspec-schemas --skill openspec-bulk-archive-change-intent-driven-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archive completed changes in OpenSpec in a single operation to reduce manual overhead and keep your workspace organized.

Core Features & Use Cases

  • Batch-archive multiple changes at once, handling conflicts intelligently and preserving a clear history.
  • Move archived changes to openspec/changes/archive with a current date stamp, while preserving important configuration files.
  • Use case: you finished several parallel changes and want to clean the active list while maintaining traceability.

Quick Start

Run a batch-archive to move all completed changes into the dated archive directory.

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 archive multiple OpenSpec changes at once, you can batch-archive all completed changes in a single operation. This process moves them to the dated archive directory while validating artifacts, tasks, and delta specs to ensure safe file moves.

What is batch archiving in OpenSpec change lifecycle management?

Batch archiving in OpenSpec change lifecycle management is the process of moving multiple completed parallel changes to a dated archive folder. It validates artifacts and tasks, streamlines your active workspace, and preserves important configuration files.

Does batch archiving OpenSpec changes handle conflicts between parallel modifications?

Yes, batch archiving handles conflicts intelligently when multiple parallel changes are ready for archiving. It performs conflict-aware handling to ensure safe file moves and preserves history in the openspec/changes/archive directory.

How do I clean up my active OpenSpec changes list while maintaining traceability?

You can clean up your active OpenSpec changes list while maintaining traceability by running a batch-archive. This moves completed changes to a date-stamped archive directory, automatically validating delta specs and preserving configuration files.

What gets validated during a bulk archive of OpenSpec changes?

During a bulk archive of OpenSpec changes, artifacts, tasks, and delta specs are validated before execution. This validation ensures safe file moves into the openspec/changes/archive directory while preserving relevant configuration data.

When should I not use bulk archiving for my OpenSpec changes?

You should avoid bulk archiving OpenSpec changes if your parallel modifications are not fully completed or if artifacts and tasks fail validation. The process requires changes to be ready and capable of passing conflict-aware handling for safe archival.