openspec-bulk-archive-change

Archive multiple completed openspec changes with conflict resolution.

5|1|Updated Jan 31, 2026

Search Tags:#git #version control #archive #batch processing #openspec #spec management

Ready to run

npx skills add https://github.com/yuboon/ai-examples --skill openspec-bulk-archive-change-yuboon

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-bulk-archive-change
Source: https://github.com/yuboon/ai-examples/tree/main/002-springboot-mcp/.claude/skills/openspec-bulk-archive-change
Command: npx skills add https://github.com/yuboon/ai-examples --skill openspec-bulk-archive-change-yuboon

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the process of archiving multiple completed changes, especially when dealing with parallel development efforts, by intelligently handling spec conflicts.

Core Features & Use Cases

Batch Archiving: Archive several changes in a single operation.
Conflict Resolution: Intelligently resolves spec conflicts by checking the codebase for actual implementation.
Use Case: When you have finished work on several related features (e.g., different aspects of an authentication system), you can use this skill to archive them all efficiently, ensuring spec consistency.

Quick Start

Use the openspec-bulk-archive-change skill to archive all completed changes.

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 changes in a batch operation?▼

Batch archiving completed changes is automated by validating artifact status, task completion, and delta specs while resolving capability conflicts by inspecting the codebase for implementation evidence.

How does batch spec management resolve conflicts during parallel development?▼

Conflict resolution for spec management intelligently checks the codebase for actual implementation evidence to resolve capability conflicts when archiving multiple parallel development changes.

Can I archive several openspec changes at once without spec synchronization issues?▼

You can archive several openspec changes at once while ensuring spec synchronization through a consolidated status report that validates artifact status and task completion before execution.

What is the best way to handle delta spec validation before archiving parallel features?▼

The best way to handle delta spec validation is automating the inspection of artifact status and task completion, providing a consolidated status report to ensure spec consistency before execution.

Does batch archiving check the codebase for actual implementation evidence?▼

Batch archiving does check the codebase for actual implementation evidence to intelligently resolve capability conflicts and ensure spec synchronization across multiple completed changes.

When should I use batch archiving for openspec changes?▼

Use batch archiving for openspec changes when you have finished work on several related features in parallel and need to efficiently archive them all while ensuring spec consistency.