skills.rest
wtg42
wtg42COMMUNITY
Explore all skills by this author →
GitHub

openspec-bulk-archive-change

Archive multiple openspec changes and resolve delta capability spec conflicts.

Updated Dec 25, 2025
Search Tags:#cli#archive#conflict-resolution#openspec#repo-management#spec-sync#batch-operation
One-click install
npx skills add https://github.com/wtg42/tty-clock-timer --skill openspec-bulk-archive-change-wtg42
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-bulk-archive-change
Source: https://github.com/wtg42/tty-clock-timer/tree/main/.opencode/skills/openspec-bulk-archive-change
Command: npx skills add https://github.com/wtg42/tty-clock-timer --skill openspec-bulk-archive-change-wtg42

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Many completed changes accumulate in openspec/changes and require manual verification, spec reconciliation, and repeated file operations to archive safely. This Skill reduces the manual effort and risk by validating artifacts and tasks, detecting spec conflicts across changes, and resolving them by checking the codebase before moving changes to an archive location.

Core Features & Use Cases

  • Interactive selection of one or many active changes with an explicit, non-automatic user prompt.
  • Batch validation of artifact completion, task lists, and delta specs for each selected change.
  • Conflict detection and agentic resolution by mapping capabilities touched by multiple changes and inspecting the codebase to determine which specs are implemented.
  • Spec sync & archival that applies resolved spec merges in the correct order and moves change directories to openspec/changes/archive/YYYY-MM-DD-<name>.
  • Comprehensive reporting showing per-change status, warnings, successes, skips, and failures.
  • Use case: When multiple parallel feature changes touch the same capability, run this Skill to confirm implementations, resolve spec conflicts, and archive completed changes in a single, auditable operation.

Quick Start

Archive selected changes interactively, resolving spec conflicts by scanning the repository and syncing implemented delta specs before moving each change to the archive directory.

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 completed openspec changes that have conflicting specs?▼

Batch-archive completed openspec changes by interactively selecting them, validating artifacts, detecting delta spec conflicts across changes, and resolving them by scanning the codebase before moving directories to openspec/changes/archive.

What is the best way to resolve capability spec conflicts across parallel openspec changes?▼

Resolve capability spec conflicts by mapping capabilities touched by multiple changes and inspecting the codebase to determine which delta specs are actually implemented, then applying the resolved spec merges in the correct order.

How do I archive multiple openspec change directories without losing completed task validations?▼

Archive multiple openspec change directories safely by running batch validation of artifact completion and task lists for each selected change before moving them to the archive directory, ensuring no uncompleted tasks are missed.

Do I need the openspec CLI to sync and consolidate delta capability specs?▼

Yes, you need the openspec CLI and repository access to openspec/changes and specs to run status checks, validate delta specs, and move or rename change directories for archiving.

Can I automatically archive all active openspec changes at once?▼

No, archiving is not automatic; the Skill uses an explicit, interactive selection prompt requiring you to select one or many active changes before validating and moving them to the archive location.

Why does batch archiving openspec changes require checking the codebase before moving directories?▼

Checking the codebase is required to resolve spec conflicts agenticly by determining which delta specs are actually implemented, ensuring the correct spec merges are applied before moving change directories to the archive.

Related Skills

Explore More Software Engineering Skills→
daodaoedudaodaoedu

openspec-archive-change

Archive completed OpenSpec change directories after validating artifacts and tasks.

Official
Advanced
EchoNoReturnEchoNoReturn

openspec-archive-change

Archives a completed change after verifying artifacts and tasks are finished.

Community
Advanced
jankneumannjankneumann
4

openspec-archive-change

Archive completed OpenSpec change directories to a dated location.

Community
Advanced
wishx127wishx127

openspec-bulk-archive-change

Archive multiple completed OpenSpec changes after reviewing artifacts and resolving conflicts.

Community
Advanced