openspec-bulk-archive-change

Name: openspec-bulk-archive-change
Availability: InStock
Author: Maplume

Archive multiple completed OpenSpec changes into dated directories with conflict resolution.

Updated Jan 13, 2026

Search Tags:#automation #codebase #conflict-resolution #openspec #change-management #delta-specs #bulk-archive

Ready to run

npx skills add https://github.com/MaplumeX/Blockwise --skill openspec-bulk-archive-change-maplumex

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archive and organize multiple completed changes in batch, reducing manual effort and preserving the codebase state with a consistent archival workflow.

Core Features & Use Cases

Batch archive: move multiple completed changes into a dated archive directory, preserving their history and .openspec.yaml.
Conflict-aware: detects delta-spec conflicts and resolves based on implemented evidence in the codebase.
User-confirmed operations: prompts for selection and a single batch confirmation to ensure intentional archiving.

Quick Start

Select the active changes to archive in a single batch and confirm to execute the archival process.

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 batch archive completed OpenSpec changes in a single operation?▼

Batch archive completed OpenSpec changes by selecting multiple active changes and confirming a single operation to move them into a dated archive directory. This process preserves configuration metadata and spec history during the move.

How does conflict resolution work when archiving multiple OpenSpec changes at once?▼

Conflict resolution during OpenSpec bulk archiving detects delta-spec conflicts and resolves them automatically based on implemented evidence found in the codebase, ensuring spec synchronization remains accurate across changes.

What is the best way to archive multiple codebase changes without losing configuration metadata?▼

Archiving multiple codebase changes using a bulk operation moves completed items into a dated directory while preserving their history and .openspec.yaml files, maintaining consistent configuration metadata across the archive.

Can I select specific OpenSpec changes to archive instead of processing all active changes?▼

Yes, the bulk archiving process prompts for user-selected changes, allowing you to specify exactly which active OpenSpec changes to include before executing a single batch confirmation to move them.

Does OpenSpec bulk archiving require manual confirmation before moving changes to the archive directory?▼

OpenSpec bulk archiving requires user-confirmed operations, prompting you to select active changes and provide a single batch confirmation to ensure the archival process is intentional before execution.

When should I avoid using bulk archiving for OpenSpec change management?▼

Avoid bulk archiving when active OpenSpec changes lack implemented evidence in the codebase, as the conflict resolution mechanism relies on this evidence to safely sync delta-specs during the batch move.