openspec-bulk-archive-change

Batch-archive multiple OpenSpec changes with conflict-aware delta-spec syncing.

33|5|Updated Feb 24, 2026
One-click install
npx skills add https://github.com/thelegendtubaguy/Qidi-Max-4-Optimized --skill openspec-bulk-archive-change-thelegendtubaguy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-bulk-archive-change
Source: https://github.com/thelegendtubaguy/Qidi-Max-4-Optimized/tree/main/.pi/skills/openspec-bulk-archive-change
Command: npx skills add https://github.com/thelegendtubaguy/Qidi-Max-4-Optimized --skill openspec-bulk-archive-change-thelegendtubaguy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archives multiple OpenSpec changes in a single operation, simplifying bulk management of parallel changes.

Core Features & Use Cases

  • Batch-archive multiple changes at once with automatic delta-spec syncing and conflict resolution.
  • Prompt selection of active changes to include, with validation and status reporting before commits.
  • Apply specs in a defined order when conflicts exist, and preserve change history and archive structure.

Quick Start

Select the active changes you want archived, then confirm the batch operation.

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 batch-archive multiple OpenSpec changes in a single operation by selecting the active changes you want included and confirming the bulk operation to move them to the archive directory.

How does bulk archiving handle delta spec conflicts?

Bulk archiving handles delta spec conflicts by inspecting the active changes, identifying conflicts, and applying the specs in a defined order before moving them to the archive directory.

Can I preserve .openspec.yaml when batch-archiving changes?

Yes, batch-archiving changes preserves the .openspec.yaml file and the overall change history while moving the selected active changes to the archive directory.

What is the best way to manage multiple parallel OpenSpec changes?

The best way to manage multiple parallel OpenSpec changes is using a bulk archive operation that provides prompt selection, validation, and status reporting before committing the batch move.

Do I need to resolve delta spec conflicts before archiving OpenSpec changes?

No, you do not need to resolve delta spec conflicts manually beforehand; the bulk archive operation automatically identifies conflicts and decides which changes to archive and in what order.