skills.rest
JanuaryLabs
JanuaryLabsOFFICIAL
Explore all skills by this author →
WebsiteGitHub

openspec-bulk-archive-change

Archive multiple completed openspec changes with validation and conflict resolution.

4|Updated Oct 10, 2025
Search Tags:#automation#archive#conflict-resolution#openspec#change-management#batch-archive#spec-sync
One-click install
npx skills add https://github.com/JanuaryLabs/deepagents --skill openspec-bulk-archive-change-januarylabs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-bulk-archive-change
Source: https://github.com/JanuaryLabs/deepagents/tree/main/.claude/skills/openspec-bulk-archive-change
Command: npx skills add https://github.com/JanuaryLabs/deepagents --skill openspec-bulk-archive-change-januarylabs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines the tedious and error-prone process of archiving many completed openspec changes at once by validating artifacts and tasks, detecting spec overlaps, and resolving conflicts before moving changes into an archive folder.

Core Features & Use Cases

  • List and select changes: Enumerates active openspec changes and lets users multi-select the set to archive.
  • Comprehensive validation: Checks artifact statuses, task completion, and delta specs for each selected change.
  • Conflict detection and agentic resolution: Identifies capability-level spec conflicts across changes and inspects the codebase to determine which specs are actually implemented, choosing order or skipping sync as appropriate.
  • Safe archival with tracking: Syncs delta specs when appropriate, moves change directories into openspec/changes/archive/YYYY-MM-DD-<name>, preserves .openspec.yaml, and summarizes successes, skips, and failures.
  • Use case: Archive multiple parallel feature changes at the end of a sprint while ensuring only implemented specs are merged and conflicts are resolved.

Quick Start

Use the openspec-bulk-archive-change skill to batch-archive selected completed changes, resolve any spec conflicts by inspecting the codebase, and move them into 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 batch archive completed openspec changes without causing spec conflicts?▼

To batch archive openspec changes safely, the skill validates artifact statuses, checks task completion, detects delta spec conflicts, and inspects the codebase to resolve them before moving directories into openspec/changes/archive with dated folder names.

What is the best way to resolve delta spec conflicts when archiving multiple changes at once?▼

Resolving delta spec conflicts during bulk archival requires inspecting the codebase to determine which specs are actually implemented, allowing the process to choose archival order or skip syncing as appropriate for overlapping capabilities.

Can I archive parallel feature changes at the end of a sprint while ensuring only implemented specs are merged?▼

Yes, you can archive parallel feature changes by multi-selecting completed changes, validating their artifacts and tasks, and syncing only the implemented delta specs before moving them into the archive directory.

How does the bulk archival process handle incomplete tasks or unmerged artifacts?▼

The bulk archival process validates artifact statuses and task completion for each selected change, skipping or flagging changes that do not meet validation requirements and summarizing all successes, skips, and failures at the end.

Do I need an openspec-managed repository to use batch change archival?▼

Yes, batch change archival applies to openspec-managed repositories, as it relies on the openspec directory structure to list active changes, preserve .openspec.yaml files, and move completed changes into openspec/changes/archive.

What limitations should I expect when consolidating parallel changes with overlapping capability specs?▼

When consolidating parallel changes with overlapping capability specs, the archival process may skip syncing delta specs if codebase inspection determines the specs are not actually implemented, resulting in skipped changes that require manual resolution.

Related Skills

Explore More Software Engineering Skills→
anssipanssip
26

openspec-bulk-archive-change

Batch-archive multiple completed Openspec changes with conflict detection.

Community
Advanced
joannanowakowskajoannanowakowska

openspec-archive-change

Archive completed OpenSpec changes after validating artifacts and task completion.

Community
Advanced
accidental-hedge-fundaccidental-hedge-fund
3

openspec-archive-change

Archive completed openspec experimental changes to dated directories with validation.

Official
Intermediate
inspedralbesinspedralbes

openspec-bulk-archive-change

Batch-archive completed OpenSpec changes and resolve delta-spec conflicts.

Official
Advanced