skills.rest
wzyxdwll
wzyxdwllCOMMUNITY
Explore all skills by this author →
GitHub

openspec-bulk-archive-change

Batch-archive completed openspec changes while preserving specs and artifacts.

14|1|Updated May 6, 2026
Search Tags:#automation#openspec#changes#specs#conflicts#batch-archive
One-click install
npx skills add https://github.com/wzyxdwll/ccgx-workflow --skill openspec-bulk-archive-change-wzyxdwll
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-bulk-archive-change
Source: https://github.com/wzyxdwll/ccgx-workflow/tree/main/.agents/skills/openspec-bulk-archive-change
Command: npx skills add https://github.com/wzyxdwll/ccgx-workflow --skill openspec-bulk-archive-change-wzyxdwll

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Batch-archive multiple completed openspec changes while preserving specs and artifacts.

Core Features & Use Cases

  • Supports conflict-aware batch archiving of parallel changes.
  • Validates artifact statuses and task completion before archiving.
  • Archives changes under openspec/changes/archive/YYYY-MM-DD-<name>, preserving original configuration.

Quick Start

Initiate a batch archive by selecting active changes and confirming the operation.

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 multiple completed openspec changes?▼

You can batch-archive multiple completed openspec changes by scanning active changes via openspec list --json, selecting targets, resolving delta-spec conflicts, and moving them to openspec/changes/archive/YYYY-MM-DD-<name>.

How does conflict-aware batching work for openspec parallel changes?▼

Conflict-aware batching inspects the codebase to resolve delta-spec conflicts among parallel changes, validating artifact statuses and task completion checks before safely archiving the selected openspec changes.

Do I need to validate task completion before archiving openspec changes?▼

Yes, validating artifact statuses and task completion checks is required before archiving openspec changes to ensure only fully completed parallel changes are moved to the archive directory.

What is the best way to archive openspec changes while preserving specs and artifacts?▼

The best way is using conflict-aware batch archiving, which moves completed changes under openspec/changes/archive/YYYY-MM-DD-<name> while preserving the original .openspec.yaml configuration and artifacts.

Can I archive openspec changes without losing the original configuration?▼

Yes, archiving changes preserves the original .openspec.yaml configuration by moving the entire change directory under openspec/changes/archive/YYYY-MM-DD-<name> during the batch operation.

Why does batch archiving openspec changes require resolving delta-spec conflicts?▼

Resolving delta-spec conflicts is required because parallel changes managed with openspec may alter the same specs, and inspecting the codebase ensures no conflicting deltas are archived together.

Related Skills

Explore More Software Engineering Skills→
cynkracynkra
1

openspec-bulk-archive-change

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

Official
Advanced
QuafadasQuafadas
13

openspec-archive-change

Archive completed OpenSpec changes after validating artifacts, tasks, and delta specs.

Community
Advanced
emergent-companyemergent-company
1

openspec-bulk-archive-change

Archive multiple completed changes with openspec CLI after validating status and resolving conflicts.

Official
Advanced
moogahmoogah

opsx-bulk-archive

Archive multiple completed changes with conflict resolution into date-stamped folders.

Community
Advanced