openspec-bulk-archive-change

Archive multiple completed changes and resolve specification conflicts from code implementations.

1|Updated May 26, 2025
One-click install
npx skills add https://github.com/StrayDragon/llman --skill openspec-bulk-archive-change-straydragon
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-bulk-archive-change
Source: https://github.com/StrayDragon/llman/tree/main/.claude/skills/openspec-bulk-archive-change
Command: npx skills add https://github.com/StrayDragon/llman --skill openspec-bulk-archive-change-straydragon

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 simultaneously, especially when dealing with numerous parallel development efforts.

Core Features & Use Cases

  • Batch Archiving: Archive several completed changes in a single operation.
  • Conflict Detection & Resolution: Intelligently identifies and helps resolve specification conflicts between changes by analyzing code implementations.
  • Use Case: When you have finished work on several related features, this skill allows you to archive them all efficiently, ensuring that any overlapping specification changes are handled correctly based on their implementation status and creation time.

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 version control repository at once?

You can archive multiple completed changes at once by using batch archiving operations. This streamlines the process of archiving numerous parallel development efforts simultaneously, resolving specification conflicts by analyzing code repository implementations.

How does bulk archiving resolve specification conflicts between overlapping changes?

Bulk archiving resolves specification conflicts by analyzing code repository implementations. It intelligently identifies overlapping changes and resolves them based on artifact status, task completion, and delta specifications.

When do I need batch archiving for completed change management?

You need batch archiving when you have finished work on several related features and want to archive them all efficiently. This ensures overlapping specification changes are handled correctly based on their implementation status and creation time.

What is the best way to handle specification conflicts when archiving parallel development efforts?

The best way to handle specification conflicts when archiving parallel efforts is to use intelligent conflict resolution based on artifact status and task completion. This analyzes code implementations to ensure overlapping changes are handled correctly during batch operations.

Does batch archiving work with delta specifications and existing artifact status?

Yes, batch archiving works with delta specifications and existing artifact status. It uses these elements to intelligently detect and help resolve specification conflicts between changes during the bulk archiving process.