openspec-bulk-archive-change

Archive multiple OpenSpec changes with conflict detection and spec syncing.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/daodaoedu/daodao --skill openspec-bulk-archive-change-daodaoedu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-bulk-archive-change
Source: https://github.com/daodaoedu/daodao/tree/main/.gemini/skills/openspec-bulk-archive-change
Command: npx skills add https://github.com/daodaoedu/daodao --skill openspec-bulk-archive-change-daodaoedu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines the tedious and error-prone process of archiving multiple completed OpenSpec changes by validating artifacts and tasks, detecting conflicting delta specs, and resolving conflicts against the codebase before moving changes to an archive.

Core Features & Use Cases

  • Batch selection and validation: List active changes, inspect artifact and task completion, and summarize per-change readiness.
  • Conflict detection and agentic resolution: Identify overlapping capability deltas, search the codebase for implementation evidence, and determine which specs to sync and in what order.
  • Safe archival with reporting: Move selected changes into a dated archive folder, optionally sync delta specs to main specs, and produce a detailed summary of successes, skips, and failures.
  • Use Case: When several parallel changes touch shared capabilities, use this Skill to reconcile implementations, sync the correct specs, and archive completed work in one operation.

Quick Start

Run the openspec-bulk-archive-change skill and select the changes to archive when prompted.

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 without spec conflicts?

Batch-archiving completed OpenSpec changes validates tasks and artifacts, detects delta spec conflicts, searches the codebase for implementation evidence, and moves reconciled changes into dated archive directories.

How does conflict resolution work when syncing delta specs for parallel changes?

Conflict resolution identifies overlapping capability deltas, searches the codebase for implementation evidence, and determines the correct spec sync order to reconcile parallel changes before archival.

Can I sync delta specs to main specs during a batch archive?

Yes, you can optionally sync delta specs to main specs via the openspec CLI during the batch archival process, moving reconciled changes into dated archive directories.

What is the best way to reconcile parallel changes that touch shared capabilities before release?

The best way is a conflict-aware batch operation that validates artifacts, resolves delta spec conflicts against the codebase, syncs specs in the correct order, and archives completed work in one action.

Do I need the openspec CLI to archive changes and sync specs?

Yes, the openspec CLI is required for syncing delta specs to main specs during the batch archival process, which then moves reconciled changes to dated archive directories.

What happens if artifact and task validation fails during batch archival?

Failed artifact and task validation skips incomplete changes, and the batch archival operation produces a detailed summary report highlighting successes, skips, and failures for the selected batch.