openspec-bulk-archive-change

Archive multiple completed OpenSpec changes in a single batch operation.

114|47|Updated Apr 13, 2026
One-click install
npx skills add https://github.com/huangjia2019/sdd-in-action --skill openspec-bulk-archive-change-huangjia2019
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-bulk-archive-change
Source: https://github.com/huangjia2019/sdd-in-action/tree/main/week2/code/.opencode/skills/openspec-bulk-archive-change
Command: npx skills add https://github.com/huangjia2019/sdd-in-action --skill openspec-bulk-archive-change-huangjia2019

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines the repetitive and error-prone task of archiving multiple completed OpenSpec changes at once, providing a single workflow to validate artifacts and tasks, detect spec conflicts, and make intelligent decisions about which specs to sync before archiving.

Core Features & Use Cases

  • Bulk selection and validation: List active changes, inspect artifact completion and task checklists, and summarize readiness before any destructive action.
  • Spec conflict detection and resolution: Detect capability-level conflicts across delta specs and resolve them by inspecting the codebase to determine which changes are implemented or which order to apply.
  • Safe archival with tracking: Move confirmed changes into a dated archive directory while preserving metadata and reporting per-change outcomes (archived, skipped, failed).
  • Use Case: When multiple teams have parallel changes touching the same capabilities, use this Skill to ensure only implemented specs are synced and to archive completed changes reliably.

Quick Start

Archive selected OpenSpec changes, resolve any spec conflicts by inspecting the codebase, and move confirmed changes to openspec/changes/archive/YYYY-MM-DD-<name>.

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 without causing spec conflicts?

Batch-archive OpenSpec changes by validating artifact completion, detecting capability-level delta spec conflicts, and inspecting the codebase to sync implemented specs before moving confirmed changes to a dated archive directory.

What is the best way to resolve delta spec conflicts when archiving parallel OpenSpec changes?

Resolve delta spec conflicts during OpenSpec archival by inspecting the codebase to determine which parallel changes are actually implemented, ensuring only verified specs are synced before moving changes to the archive.

How does bulk change archival handle incomplete tasks or unimplemented specs in OpenSpec repositories?

Bulk change archival validates artifact and task checklists, summarizing readiness before any destructive action and reporting per-change outcomes as archived, skipped, or failed to prevent incomplete specs from being moved.

Can I use batch archival for OpenSpec changes when multiple teams modify the same capabilities?

Batch archival coordinates OpenSpec changes when multiple teams modify the same capabilities by detecting spec conflicts, verifying codebase implementation status, and safely archiving only confirmed completed changes.

What happens to OpenSpec metadata when changes are moved to a dated archive directory?

Metadata is preserved when changes are moved to a dated archive directory, ensuring tracking and historical context remain intact while reporting the outcome of each archived, skipped, or failed change.

When should I avoid batch archiving completed OpenSpec changes?

Avoid batch archiving when active changes lack completed tasks or when delta spec conflicts cannot be verified against the codebase, as the process skips unconfirmed changes to prevent syncing unimplemented specs.