openspec-bulk-archive-change

Archive multiple completed OpenSpec changes with conflict detection and status reporting.

2|Updated Feb 5, 2026
One-click install
npx skills add https://github.com/dshearer/misatay --skill openspec-bulk-archive-change-dshearer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-bulk-archive-change
Source: https://github.com/dshearer/misatay/tree/main/.claude/skills/openspec-bulk-archive-change
Command: npx skills add https://github.com/dshearer/misatay --skill openspec-bulk-archive-change-dshearer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archive multiple completed changes at once to simplify management of OpenSpec changes and keep the workspace clean, reducing manual rework and drift.

Core Features & Use Cases

  • Batch-archive: select multiple changes and move them to the archive directory in a single operation.
  • Conflict resolution: detects overlapping delta specs and resolves them by inspecting the codebase and applying in the appropriate order.
  • Status reporting: produces a consolidated per-change status summary before execution.
  • Safety and preservation: preserves important configuration files (e.g., .openspec.yaml) during archiving.
  • Partial failures: continues archiving other changes if one change fails, with clear failure notes.

Quick Start

Select the changes to archive when prompted, then confirm to complete the bulk 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 bulk archive completed OpenSpec changes in one pass?

To bulk archive completed OpenSpec changes, select multiple changes and move them to the archive directory in a single operation. This streamlines project history and keeps your workspace clean by reducing manual rework and drift.

What happens when delta specs touch the same capabilities during a bulk archive?

When delta specs touch the same capabilities during a bulk archive, the process detects overlapping conflicts. It resolves them by inspecting the codebase and applying the changes in the appropriate order to ensure safe archival.

How are partial failures handled when archiving multiple changes concurrently?

During concurrent archival, partial failures are handled by continuing to archive other changes if one fails. The process provides clear failure notes and a consolidated per-change status summary before execution.

Does bulk archiving OpenSpec changes preserve configuration files?

Bulk archiving OpenSpec changes preserves important configuration files like .openspec.yaml. This safety mechanism ensures your project configurations remain intact while moving completed changes to the archive directory.

Why do I need to batch archive OpenSpec changes instead of moving them individually?

Batch archiving OpenSpec changes simplifies management by handling multiple changes concurrently, reducing manual rework. It detects conflicts across delta specs and executes safe archival with per-change status reporting.