openspec-bulk-archive-change

Archive multiple completed OpenSpec changes with conflict detection and per-change outcomes.

Updated Jan 29, 2026

Search Tags:#automation #conflict-resolution #openspec #change-management #bulk-archive #spec-delta

Ready to run

npx skills add https://github.com/hongquandev/OpenSpec-VI --skill openspec-bulk-archive-change-hongquandev

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-bulk-archive-change
Source: https://github.com/hongquandev/OpenSpec-VI/tree/main/.agent/skills/openspec-bulk-archive-change
Command: npx skills add https://github.com/hongquandev/OpenSpec-VI --skill openspec-bulk-archive-change-hongquandev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archive multiple completed OpenSpec changes in a single operation to streamline change management and reduce manual overhead when handling multiple concurrent changes.

Core Features & Use Cases

Bulk selection: retrieve active changes via openspec list --json and choose one or more changes, with an "All changes" option to simplify large batch scenarios.
Conflict-aware archiving: for each selected change, analyze artifact status, tasks completion, and delta specs across changes to detect conflicts and guide resolution using codebase inspection.
Safe, auditable archiving: preserve the original OpenSpec metadata, move changes to archive/YYYY-MM-DD-<name>, and generate per-change outcomes for traceability and rollback if needed.

Quick Start

Select the active changes you want to archive and run the bulk archive workflow to move them into the archive directory.

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 instead of one by one?▼

Bulk-archive multiple OpenSpec changes by listing active changes via openspec list --json, selecting batches or all changes, evaluating artifact status and delta specs, resolving conflicts, and moving them to archive/YYYY-MM-DD-<name>.

What happens if two completed changes have conflicting delta specs during bulk archival?▼

During bulk archival, conflict-aware analysis inspects artifact status, task completion, and delta specs across selected changes to detect conflicts and guide intelligent resolution using codebase inspection before proceeding.

Can I archive all active OpenSpec changes in a single operation?▼

Yes, bulk-archive supports an "All changes" option to simplify large batch scenarios, retrieving active changes and processing them together with conflict detection and per-change outcome summaries.

How does bulk archiving ensure safe rollback for completed change management?▼

Bulk archiving preserves original OpenSpec metadata, moves changes to dated archive directories, generates per-change outcome summaries for traceability, and requires explicit user confirmation before finalizing any archival operation.

What needs to be validated before archiving OpenSpec changes in bulk?▼

Before bulk archival, the workflow validates artifact states, task completion status, and delta specs for each selected change, surfacing any conflicts and applying resolution logic before moving files to the archive directory.

Why does bulk archiving require explicit confirmation for OpenSpec change management?▼

Explicit user confirmation serves as a guardrail to ensure safe, auditable archiving, preventing unintended bulk operations while producing per-change outcomes for traceability and potential rollback.