openspec-bulk-archive-change

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

Archive multiple active OpenSpec changes after validating task completion and resolving delta-spec conflicts.

1|1|Updated May 5, 2026

Search Tags:#Claude Code #archive #conflict resolution #change management #openspec #spec sync

Ready to run

npx skills add https://github.com/cynkra/cynkra.ai.day --skill openspec-bulk-archive-change-cynkra

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines the cleanup of many completed OpenSpec changes by safely archiving them in a batch while reducing spec inconsistencies from parallel work.

Core Features & Use Cases

Batch change archiving: Archives multiple active changes in one operation, reducing repetitive manual steps.
Status-aware decisioning: Validates artifacts and task completion, warning when changes are incomplete.
Conflict detection and resolution: Detects overlapping capability specs across selected changes and resolves by checking implementation and applying specs in a sensible order.

Quick Start

Ask the AI to run openspec-bulk-archive-change to list active OpenSpec changes, let you multi-select them, then archive the chosen changes with conflict-aware spec synchronization.

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?▼

Batch archiving OpenSpec changes involves listing active changes via the openspec CLI, inspecting their task completion status, resolving any delta-spec conflicts, and moving them to a dated archive directory while continuing past failures.

What happens if parallel OpenSpec changes have overlapping capability specs?▼

Overlapping capability specs are detected during the batch archive process and resolved by checking codebase implementation evidence, then applying the delta specs in a sensible order to ensure consistent spec state before moving changes to the archive.

Can I archive OpenSpec changes that have incomplete tasks or artifacts?▼

Archiving incomplete OpenSpec changes triggers a warning from the status-aware validation system, which checks artifact and task completion status before allowing the batch operation to continue past failures and move changes to the archive.

Why do I need to sync delta specs before archiving OpenSpec changes in bulk?▼

Delta spec synchronization is required before bulk archiving because parallel changes touching the same capabilities can create spec inconsistencies, and syncing ensures a consistent spec state before moving changes under the openspec/changes/archive directory.

What is the best way to clean up many completed OpenSpec changes?▼

Batch archiving is the best approach for cleanup, as it safely archives multiple active OpenSpec changes by validating completion, resolving overlapping capability spec conflicts via codebase evidence, and moving changes to a dated archive directory.

Does the openspec CLI support continuing past archive failures?▼

Yes, the openspec CLI bulk archive operation continues past failures, moving each valid change to a dated archive directory while warning about incomplete tasks or unresolved conflicts, ensuring one failure does not block the entire batch.