openspec-bulk-archive-change

Archive multiple completed OpenSpec changes with conflict-aware spec synchronization.

Updated May 5, 2026
One-click install
npx skills add https://github.com/agoodway/goodday --skill openspec-bulk-archive-change-agoodway
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-bulk-archive-change
Source: https://github.com/agoodway/goodday/tree/main/.opencode/skills/openspec-bulk-archive-change
Command: npx skills add https://github.com/agoodway/goodday --skill openspec-bulk-archive-change-agoodway

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you archive many completed OpenSpec changes in one go while reducing the risk of losing or overwriting the wrong spec updates.

Core Features & Use Cases

  • Batch archive with guided selection: Lists active changes and prompts you to multi-select what to archive, including an “All changes” option without auto-selecting.
  • Pre-flight validation per change: Checks artifact completion, task completion from tasks.md, and detects which delta capability specs exist for each change.
  • Conflict-aware spec syncing: Detects capability-level conflicts across selected changes and resolves them by inspecting what is actually implemented in the codebase, applying specs in chronological order when both are present.
  • Consolidated status and safe confirmation: Shows a per-change status table, warns about incomplete changes, and uses a single confirmation for the entire batch before executing.

Quick Start

Archive all completed OpenSpec changes by selecting them from the multi-select prompt, confirming the batch archive, and letting the skill sync any applicable delta specs before moving each change into the dated archive folder.

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 archive multiple OpenSpec changes by selecting them from a multi-select prompt, confirming the batch, and letting the workflow sync delta specs before moving each change into a dated archive folder.

What is conflict-aware spec synchronization in OpenSpec?

Conflict-aware spec syncing detects capability-level conflicts across selected changes and resolves them by inspecting the actual codebase implementation, applying specs chronologically when multiple changes affect the same capability.

How does OpenSpec validate changes before a bulk archive?

OpenSpec performs pre-flight validation per change by checking artifact completion, verifying task completion from tasks.md, and detecting which delta capability specs exist before allowing archival.

Does the bulk archive skill auto-select all changes for archiving?

No, the skill lists active changes and includes an “All changes” option but does not auto-select, requiring you to manually multi-select changes for batch archiving.

What happens to the .openspec.yaml file when archiving OpenSpec changes?

During archival, the skill moves openspec/changes/<name> into openspec/changes/archive/YYYY-MM-DD-<name> while preserving the .openspec.yaml file within the archived structure.

Can I archive incomplete OpenSpec changes using bulk archive?

The skill shows a consolidated status table and warns about incomplete changes, but you still confirm the entire batch, meaning you can proceed with archiving incomplete changes after acknowledging the warnings.