openspec-bulk-archive-change

Archive multiple completed OpenSpec changes with conflict resolution and spec syncing.

Updated Feb 6, 2024
One-click install
npx skills add https://github.com/081595/mynode --skill openspec-bulk-archive-change-081595
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-bulk-archive-change
Source: https://github.com/081595/mynode/tree/main/myproject/.github/skills/openspec-bulk-archive-change
Command: npx skills add https://github.com/081595/mynode --skill openspec-bulk-archive-change-081595

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines the manual, error-prone work of archiving multiple completed OpenSpec changes by validating artifacts and tasks, detecting and resolving spec conflicts, syncing implemented specs, and moving change folders into a dated archive location.

Core Features & Use Cases

  • Batch selection and validation: List active changes, let the user pick one or many, and collect artifact, task, and delta-spec status for each.
  • Conflict detection and agentic resolution: Identify capabilities touched by multiple changes, inspect delta specs and the codebase to determine which specs are implemented, and decide application order.
  • Spec sync and safe archiving: Sync resolved delta specs intelligently, move change folders to a dated archive location, and report per-change outcomes (archived, skipped, failed).
  • Use Case: A release manager needs to archive several completed feature changes at once while ensuring only implemented specs are merged and conflicting changes are applied in the correct order.

Quick Start

Archive selected completed changes, resolve spec conflicts by inspecting the codebase, sync implemented delta specs, and move confirmed changes to openspec/changes/archive with a dated folder.

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 safely?

Batch archiving completed OpenSpec changes requires the openspec CLI and repository workspace access to validate artifacts, resolve spec conflicts, sync delta specs, and move change folders to a dated archive location during release housekeeping.

How does spec conflict resolution work when archiving multiple changes?

Spec conflict resolution identifies capabilities touched by multiple changes, inspects delta specs and the codebase to determine which specs are implemented, and decides the correct application order before syncing delta specs and archiving.

What do I need to archive OpenSpec changes in bulk?

Archiving OpenSpec changes in bulk requires the openspec CLI, repository workspace access to openspec/changes and source code, and interactive user confirmation for selecting changes and resolving conflicts during the batch operation.

Can I archive only implemented specs and skip incomplete changes?

Yes, the batch archive process inspects the codebase to determine which delta specs are implemented, syncing only resolved specs and reporting per-change outcomes as archived, skipped, or failed based on validation status.

What happens if spec conflicts are detected during batch change archiving?

When spec conflicts are detected during batch archiving, the Skill inspects delta specs and the codebase to determine implementation status, decides application order, and requires interactive user confirmation to resolve the conflicts before proceeding.