openspec-bulk-archive-change

Archive multiple completed OpenSpec changes and resolve spec conflicts via codebase analysis.

30|1|Updated Feb 18, 2026

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

Ready to run

npx skills add https://github.com/pacaplan/flokay --skill openspec-bulk-archive-change-pacaplan

💬 Prompt for ChatGPT / Claude Chat▼

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

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 in OpenSpec, preventing manual effort and potential errors when dealing with numerous parallel updates.

Core Features & Use Cases

Batch Archiving: Archive several changes simultaneously.
Conflict Resolution: Intelligently handles spec conflicts by checking the codebase for actual implementation.
Use Case: After completing several related features, use this skill to archive them all at once, ensuring that spec conflicts are resolved correctly based on what has actually been coded.

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 OpenSpec changes at once after parallel development?▼

To archive multiple OpenSpec changes at once, use the batch archiving skill to process completed changes simultaneously. It intelligently resolves spec conflicts by analyzing the codebase for actual implementation, ensuring accurate archival across parallel branches.

How does spec conflict resolution work during bulk archiving?▼

Spec conflict resolution during bulk archiving works by checking the codebase for actual implementation. Instead of manual checks, the skill analyzes the code to verify which specifications were truly coded, resolving discrepancies automatically before completing the archival.

Do I need the OpenSpec CLI to batch archive completed changes?▼

Yes, you need the OpenSpec CLI installed to batch archive completed changes. The skill depends on the CLI to list, status, and manage change artifacts and specifications, requiring it to execute the automated bulk archival workflow.

What is the best way to handle spec conflicts when archiving numerous parallel updates?▼

The best way to handle spec conflicts when archiving numerous parallel updates is using automated bulk archival. It resolves conflicts by verifying actual codebase implementation, preventing manual effort and errors when synchronizing multiple completed branches.

Can I use batch processing to archive changes across multiple parallel branches?▼

Yes, you can use batch processing to archive changes across multiple parallel branches. The skill is designed for scenarios with numerous parallel development branches requiring synchronized archival, managing multiple change artifacts simultaneously.

Why does manual archiving fail when dealing with numerous OpenSpec change artifacts?▼

Manual archiving fails with numerous OpenSpec change artifacts because it requires significant effort and introduces potential errors. Bulk archival automation prevents these issues by intelligently resolving spec conflicts through codebase analysis across all completed changes.