openspec-bulk-archive-change

Archive multiple completed openspec changes with conflict resolution.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the tedious and error-prone process of archiving multiple completed changes at once, ensuring specs are synced correctly and conflicts are resolved before removal from the active changes list. It prevents accidental loss of implemented work and provides a clear audit of what was archived, why, and where it moved.

Core Features & Use Cases

  • Batch selection and validation: List active changes, let the user pick one or many, and collect artifact, task, and delta-spec status for each selection.
  • Conflict detection and agentic resolution: Detect capability-level spec conflicts across changes and inspect the codebase to determine which specs are actually implemented, resolving via implementation evidence or chronological ordering.
  • Safe archive execution: Confirm with the user, sync resolved specs to main specs when applicable, move change directories to a dated archive location while preserving important files, and report per-change outcomes (archived, skipped, failed).
  • Use Case: When preparing a release or cleaning up a backlog, run a single workflow to archive several parallel changes, resolve overlapping spec updates intelligently, and produce a clear summary of results.

Quick Start

Archive three completed changes after reviewing their statuses and resolving any spec conflicts.

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 openspec changes to clean up the active change list?

You can batch archive completed openspec changes by selecting multiple active changes, validating their artifacts and delta specs, resolving capability conflicts, and moving them into date-prefixed archive locations safely.

What happens when multiple completed change specs have capability conflicts during archiving?

When capability spec conflicts arise during archiving, the system inspects the codebase for implementation evidence to determine which specs are actually implemented and resolves conflicts chronologically or based on that evidence.

Can I archive several parallel changes with delta specs and artifacts at once for a release?

Yes, multiple parallel changes with delta specs and artifacts can be archived together in a single batch workflow that evaluates statuses, resolves overlapping spec updates, and produces a summary of archived, skipped, or failed changes.

Do I need the openspec CLI to run batch archive operations on completed changes?

Yes, openspec CLI access is required to read openspec/changes directories and specs, detect capability conflicts, sync resolved specs, and move change folders into date-prefixed archive locations during batch archiving.

Why does batch archiving completed changes prevent accidental loss of implemented work?

Batch archiving prevents accidental loss by confirming actions with the user, syncing resolved specs to main specs, preserving important files, and generating a clear audit trail of what was archived and where it moved.

What is the best way to clean up a backlog of completed openspec changes safely?

The best way is running a single batch archive workflow that validates selections, resolves overlapping spec updates intelligently, and reports per-change outcomes to ensure a clear audit of archived, skipped, or failed changes.