openspec-bulk-archive-change

Archive multiple openspec changes with conflict detection and resolution.

Updated Apr 11, 2025

Search Tags:#automation #devops #archive #conflict-resolution #openspec #bulk-archive #spec-sync

Ready to run

npx skills add https://github.com/pabloimrik17/monolab --skill openspec-bulk-archive-change-pabloimrik17

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill streamlines the tedious process of archiving multiple completed openspec changes by batching selection, validating status, detecting spec conflicts, and resolving them before moving change directories into an archive.

Core Features & Use Cases

Batch selection and confirmation of multiple active openspec changes to avoid repetitive single-change archives.
Consolidated status gathering including artifact states, task completion, and delta spec presence for each change.
Intelligent conflict detection across capability specs and agentic resolution by inspecting delta specs and the repository codebase to determine which specs are implemented and the correct application order.
Automated spec sync (when appropriate) and deterministic archival of change directories into a dated archive folder while tracking successes, skips, and failures.

Quick Start

Select the changes to archive, inspect the consolidated status and conflict resolutions, then confirm to batch-archive and optionally sync specs.

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 in a monorepo workflow?▼

Batch archiving completed openspec changes involves selecting multiple active changes, validating their task completion and artifact states, and moving their directories into a dated archive folder in a single operation. This avoids repetitive single-change archives in monorepo workflows.

How does conflict detection work when archiving multiple openspec delta specs?▼

Conflict detection for openspec delta specs works by inspecting the delta specs and the repository codebase to determine which capability specs are actually implemented. It then identifies the correct application order to resolve conflicts before archiving.

What do I need to run bulk archiving for openspec changes?▼

To run bulk archiving for openspec changes you need the openspec CLI installed, repository file access for inspecting spec and code states, and permission to move change directories into an archive folder within your repository.

Can I automatically sync capability specs while archiving completed openspec changes?▼

Yes, you can automatically sync capability specs while archiving completed openspec changes. The process applies automated spec syncing when appropriate, consolidating status gathering and conflict resolution before moving the change directories.

What happens if some openspec changes fail during the bulk archive process?▼

During the bulk archive process, the operation tracks successes, skips, and failures deterministically. Changes that fail validation or conflict resolution are skipped, allowing successful changes to archive without interrupting the batch operation.