openspec-bulk-archive-change

Batch archive multiple completed openspec changes with validation and conflict detection.

1|Updated Feb 22, 2026
One-click install
npx skills add https://github.com/SiddharthChillale/cloud-operations-reasoning-agent --skill openspec-bulk-archive-change-siddharthchillale
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-bulk-archive-change
Source: https://github.com/SiddharthChillale/cloud-operations-reasoning-agent/tree/main/.opencode/skills/openspec-bulk-archive-change
Command: npx skills add https://github.com/SiddharthChillale/cloud-operations-reasoning-agent --skill openspec-bulk-archive-change-siddharthchillale

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines the tedious and error-prone process of archiving multiple completed openspec changes by validating artifacts, tasks, and delta specs before moving changes to an archive. It prevents accidental loss or incorrect spec syncs by detecting capability-level conflicts and resolving them through repository inspection.

Core Features & Use Cases

  • Interactive selection and confirmation: Prompt the user to pick which changes to archive, including an "All changes" option, and require explicit confirmation before proceeding.
  • Batch validation: Collect artifact status, task completion, and delta spec contents for each selected change to build a consolidated readiness view.
  • Conflict detection and agentic resolution: Map which changes touch the same capability, inspect delta specs and the codebase for implementation evidence, and resolve ordering or selective syncs based on findings.
  • Safe archive execution and reporting: Perform spec syncs when appropriate, move change directories into a dated archive folder, and produce a per-change outcome summary with successes, skips, and failures.
  • Use case: Prepare a release by archiving a set of completed feature changes while ensuring no overlapping specs are lost or incorrectly applied.

Quick Start

Select multiple completed openspec changes, review the consolidated status and any detected conflicts, then confirm to archive the confirmed changes in one batch.

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 openspec changes at once?

Batch-archive completed openspec changes by interactively selecting multiple changes, validating their artifacts and delta specs, resolving capability conflicts, and moving them to a dated archive folder in a single operation.

What happens when parallel openspec changes have conflicting delta specs?

Conflict detection maps changes touching the same capability, inspects delta specs and the codebase for implementation evidence, and resolves ordering or selective spec syncs based on those findings before archiving.

Can I archive all completed openspec changes simultaneously instead of selecting them individually?

Yes, you can select an "All changes" option during interactive selection, which batches every completed change into a single archive operation after validating readiness and resolving any detected capability conflicts.

Does batch archiving openspec changes sync specs automatically before moving files?

Spec syncs are performed when appropriate based on conflict detection results, ensuring overlapping specs are correctly applied before change directories are moved into the dated archive folder.

Why do my openspec changes fail to archive when multiple features touch the same capability?

Archiving fails or skips when capability-level spec conflicts are detected without clear implementation evidence, requiring you to resolve ordering or selective syncs before the batch archive can safely proceed.