openspec-bulk-archive-change

Name: openspec-bulk-archive-change
Availability: InStock
Author: joannanowakowska

Archive multiple completed OpenSpec changes after validating status and conflicts.

10|Updated Jul 7, 2026

Search Tags:#cli #archive #batch processing #conflict resolution #change management #openspec

Ready to run

npx skills add https://github.com/joannanowakowska/plannning-poker-app --skill openspec-bulk-archive-change-joannanowakowska

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-bulk-archive-change
Source: https://github.com/joannanowakowska/plannning-poker-app/tree/main/.github/skills/openspec-bulk-archive-change
Command: npx skills add https://github.com/joannanowakowska/plannning-poker-app --skill openspec-bulk-archive-change-joannanowakowska

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you archive multiple finished OpenSpec changes in one coordinated operation, reducing repetitive manual work and lowering the risk of missing conflicts or incomplete updates.

Core Features & Use Cases

Bulk Change Review: Collects the status of multiple active changes, including artifacts, tasks, and delta specs.
Conflict Detection and Resolution: Identifies overlapping capability specs and checks the codebase to determine which changes are actually implemented.
Safe Archiving Workflow: Prompts for user selection and confirmation, then archives each approved change while preserving .openspec.yaml and reporting successes, skips, and failures.
Use Case: A team has several completed feature branches in OpenSpec and wants to archive them together after verifying implementation and resolving spec conflicts.

Quick Start

Ask the assistant to batch archive the completed OpenSpec changes and guide you through selection, conflict review, and confirmation.

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 batch archive completed OpenSpec changes safely?▼

Batch archiving OpenSpec changes requires the openspec CLI to collect change statuses, detect overlapping capability conflicts, and prompt for user confirmation before moving approved items.

What is the best way to resolve spec conflicts when archiving multiple OpenSpec changes?▼

Conflict resolution during OpenSpec archival involves identifying overlapping capability specs and checking the codebase to verify which parallel changes are actually implemented before proceeding.

Does the OpenSpec bulk archive process check if tasks are actually implemented?▼

Yes, the OpenSpec bulk archive workflow validates task completion and delta specs against the codebase to ensure changes are actually implemented before allowing archival.

Do I need the openspec CLI to archive multiple change directories at once?▼

Yes, the openspec CLI is required to perform batch archiving, as the Skill relies on it to validate change status, run implementation checks, and execute ordered archive operations.

What happens if an OpenSpec change is not fully implemented during batch archival?▼

If an OpenSpec change is not fully implemented, the Skill skips the archival for that item and reports it alongside successes and failures in the final summary output.