openspec-bulk-archive-change

Archive multiple OpenSpec changes after validating task completion and spec overlap.

Updated Jan 26, 2026
One-click install
npx skills add https://github.com/brandon-setegn/kafka-test --skill openspec-bulk-archive-change-brandon-setegn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-bulk-archive-change
Source: https://github.com/brandon-setegn/kafka-test/tree/main/.cursor/skills/openspec-bulk-archive-change
Command: npx skills add https://github.com/brandon-setegn/kafka-test --skill openspec-bulk-archive-change-brandon-setegn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines the tedious work of archiving many completed OpenSpec changes at once, especially when several changes touch the same capability and need conflict-aware handling.

Core Features & Use Cases

  • Batch Change Review: Summarizes artifact status, task completion, and delta specs for each selected change.
  • Conflict Detection and Resolution: Identifies overlapping capabilities across changes and determines which specs should be applied based on implementation evidence.
  • Safe Archiving Workflow: Prompts for user selection and confirmation, then archives changes while preserving clear status, warnings, and failure handling.
  • Use Case: A release manager needs to archive several finished spec changes before a cutover and wants the process to verify implementation, resolve spec overlaps, and report exactly what was archived.

Quick Start

Ask the AI to list active OpenSpec changes, compare their task and artifact status, resolve any spec conflicts, and archive the selected changes safely.

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

Batch archiving OpenSpec changes requires validating task completion, artifact status, and spec overlap before applying ordered archive operations. The process includes conflict detection, user selection, and confirmation prompts to ensure safe spec synchronization.

How does conflict resolution work when archiving spec changes that touch the same capability?

Conflict detection identifies overlapping capabilities across changes and determines which delta specs apply based on implementation evidence. This prevents incompatible spec synchronization when multiple changes modify the same functionality.

Do I need the openspec CLI to batch archive changes?

Yes, batch archiving OpenSpec changes requires openspec CLI access and codebase inspection to verify implementation status. The CLI enables ordered archive operations while the Skill handles conflict checks and user confirmation prompts.

What happens if task completion validation fails during batch change archiving?

When task completion validation fails, the workflow applies failure handling that preserves clear status and warnings for the affected changes. Failed changes are excluded from the archive operation while successful ones proceed with user confirmation.

What's the best way to prepare spec changes for batch archiving before a release cutover?

Preparing spec changes for batch archiving involves reviewing artifact status, confirming task completion, and resolving spec overlaps across all selected changes. The workflow then archives verified changes in order with explicit user confirmation at each step.