openspec-bulk-archive-change

Batch archive completed openspec changes and resolve delta spec conflicts.

Updated Jan 18, 2026

Search Tags:#software development #archival #change management #openspec #delta specs #batch archive #spec conflict resolution

Ready to run

npx skills add https://github.com/tungnguyen10/iuh_department --skill openspec-bulk-archive-change-tungnguyen10

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-bulk-archive-change
Source: https://github.com/tungnguyen10/iuh_department/tree/main/.agents/skills/openspec-bulk-archive-change
Command: npx skills add https://github.com/tungnguyen10/iuh_department --skill openspec-bulk-archive-change-tungnguyen10

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually archiving multiple completed openspec changes one by one is slow and prone to errors, especially when parallel changes have conflicting delta specs that need to be resolved before archival.

Core Features & Use Cases

Batch Archiving: Archive multiple active completed openspec changes in a single operation instead of processing each change individually.
Intelligent Conflict Resolution: Automatically detect delta spec conflicts between parallel changes and resolve them by checking the codebase for actual implementation evidence.
Use Case: When you have 3+ finished feature changes in openspec ready for archival, this skill handles spec syncing, conflict checks, and batch moving to the archive folder with clear status reporting.

Quick Start

Use the openspec-bulk-archive-change skill to batch archive all your completed active openspec changes, automatically resolving any delta spec conflicts between them.

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 completed openspec changes at once instead of one by one?▼

You can batch archive multiple completed openspec changes in a single operation to eliminate repetitive manual processing, automatically syncing delta specs and moving entries to the archive folder.

How does delta spec conflict resolution work when archiving parallel feature changes?▼

Delta spec conflict resolution works by automatically detecting conflicts between parallel changes and checking the codebase for actual implementation evidence to validate and reconcile the differences.

What is the best way to handle openspec change management for 3 or more finished features?▼

The best way to handle change management for multiple finished features is running a batch archive operation that validates completion status, resolves delta spec conflicts, and syncs specs to main.

Do I need to validate change completion status before batch archiving openspec changes?▼

Yes, the batch archive process validates the completion status of active openspec changes before proceeding to sync relevant delta specs to main specs and moving them to the archive folder.

Can I sync delta specs to main specs automatically during the batch archival process?▼

Yes, you can sync relevant delta specs to main specs automatically during the batch archival process, which also includes conflict detection and clear status report generation for the operation.

Why does manually archiving openspec changes fail when parallel features have conflicting specs?▼

Manually archiving fails because parallel changes often have conflicting delta specs that require codebase implementation checks to resolve, making individual processing slow and prone to errors.