openspec-bulk-archive-change

Batch archive completed openspec changes and sync delta specs.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines the tedious and error-prone process of archiving multiple completed change sets by batching the archive operation, validating artifact and task completion, detecting spec conflicts, and handling spec synchronization intelligently.

Core Features & Use Cases

  • Selective batch archiving: Let users choose one or more completed changes and archive them in a single operation while preserving metadata.
  • Conflict detection and agentic resolution: Identify capability-level spec conflicts across changes and determine which specs to sync by inspecting the codebase and implementation evidence.
  • Validation and reporting: Aggregate artifact statuses, task completion, delta spec details, and present a consolidated status table before confirming archives, then summarize outcomes and any failures.
  • Use Case: Ideal for software teams consolidating parallel changes before a release, ensuring only implemented specs are synced and avoiding accidental loss of in-progress work.

Quick Start

Select the completed changes to archive, review the consolidated status and conflict resolutions, and confirm the batch archive operation to move chosen change folders into the 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 batch archive completed changes in openspec without losing in-progress work?

Batch archiving completed openspec changes allows you to select multiple change sets and move them in a single operation. The process validates artifact completion, detects spec conflicts, and preserves metadata while relocating chosen directories to the archive.

How does spec conflict detection work when archiving parallel changes?

Spec conflict detection identifies capability-level conflicts across parallel changes by inspecting the codebase and implementation evidence. It determines which delta specs to sync to main specs, resolving discrepancies intelligently before confirming the archive operation.

Do I need the openspec CLI to sync delta specs to main specs during a batch archive?

Yes, the openspec CLI and repository workspace access are required to perform file operations and code search. The CLI drives the validation, conflict detection, and delta spec synchronization processes during the interactive batch archive.

What is the best way to validate artifact and task completion before archiving openspec changes?

Validating artifact and task completion before archiving involves aggregating statuses and delta spec details into a consolidated status table. This provides a clear overview for interactive user confirmation before executing the batch archive.

Can I choose which specific changes to archive when consolidating parallel openspec branches?

Selective batch archiving allows you to choose one or more completed openspec changes for relocation. You can review consolidated statuses and conflict resolutions before confirming the operation, preserving metadata throughout the process.