openspec-bulk-archive-change

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires openspec, and includes references (resource) components.

What problem does it solve?

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

Core Features & Use Cases

  • Batch Archiving: Archive several changes simultaneously.
  • Conflict Resolution: Automatically detects and resolves conflicts in capability specs by examining codebase implementations.
  • Intelligent Syncing: Applies specs based on actual implementation status and chronological order.
  • Use Case: When you have finished work on several features that touch the same API endpoint, this skill helps you archive them all at once, ensuring the correct specifications are merged without manual intervention.

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 spec changes at once without manual conflict resolution?

Batch archiving multiple completed changes is handled by analyzing codebase implementations to automatically detect and resolve capability spec conflicts. It syncs specs based on chronological order and implementation status, providing detailed summaries of archived and skipped changes.

Why do capability spec conflicts happen when archiving parallel feature changes in openspec?

Spec conflicts happen during archiving when multiple parallel development efforts touch the same API endpoint or capability. The skill resolves these by examining actual codebase implementations and applying specs according to their chronological order and completion status.

Do I need the openspec CLI installed to batch archive completed changes?

Yes, the openspec CLI is required for change management and status checks. The skill depends on this command-line interface to verify implementation status and execute the batch archiving operations within the openspec system.

What is the best way to merge specifications for several features that modify the same API endpoint?

The best way to merge specifications for overlapping features is using intelligent spec syncing. The skill examines codebase implementations to determine the correct specification merge order, eliminating manual intervention when archiving parallel changes.

How does intelligent spec syncing determine which changes to archive and which to skip?

Intelligent spec syncing determines archived versus skipped changes by analyzing actual implementation status in the codebase. It applies specs chronologically and outputs a detailed summary indicating which completed changes were successfully archived and which were skipped.