openspec-archive-change

Archive completed OpenSpec changes after validation and optional delta-spec sync.

5|Updated Apr 29, 2026
One-click install
npx skills add https://github.com/breuerfelix/spurwechsel --skill openspec-archive-change-breuerfelix
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/breuerfelix/spurwechsel/tree/main/.opencode/skills/openspec-archive-change
Command: npx skills add https://github.com/breuerfelix/spurwechsel --skill openspec-archive-change-breuerfelix

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you finalize an implemented OpenSpec change by validating completion signals and safely moving it into an archive, with optional syncing of delta specs back to the main specs.

Core Features & Use Cases

  • Change selection and validation: Lists active changes via openspec list --json, requires explicit user selection when a change name is not provided, and blocks guessing/auto-selection.
  • Completion checks before archiving: Verifies artifact completion via openspec status --change "<name>" --json, and checks task completion by counting - [ ] vs - [x] in the tasks file (e.g., tasks.md) when present.
  • Delta spec sync assessment: Detects delta specs under openspec/changes/<name>/specs/, compares them to corresponding main specs, presents a combined summary, and optionally performs syncing before archiving.
  • Safe archiving: Moves the change directory into openspec/changes/archive/YYYY-MM-DD-<change-name>/ and preserves .openspec.yaml by moving the whole directory, failing if the target already exists to prevent accidental overwrites.

Quick Start

Ask the AI to archive the completed change named "MyChange" in the experimental workflow and sync delta specs to the main specs if needed.

Frequently Asked Questions about openspec-archive-change

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I archive a completed OpenSpec change and sync delta specs?

Archive a completed OpenSpec change by running completion validation through `openspec status`, optionally syncing delta specs to main specs, then moving the directory into `openspec/changes/archive/YYYY-MM-DD-<name>/` for a safe, traceable handoff.

What validation checks are required before archiving an OpenSpec change?

Required validation checks for archiving an OpenSpec change include verifying artifact completion via `openspec status --json` and counting incomplete `- [ ]` versus completed `- [x]` checkboxes in the tasks file to ensure all tasks are finished.

Does the OpenSpec archiving process prevent accidental overwrites of existing archives?

Yes, OpenSpec archiving prevents accidental overwrites by failing the directory move operation if the target archive path `openspec/changes/archive/YYYY-MM-DD-<name>/` already exists, ensuring historical data integrity.

Can I automatically select an OpenSpec change to archive without specifying the name?

No, you cannot automatically select an OpenSpec change to archive without specifying the name; the process blocks guessing and auto-selection, requiring explicit user selection from the `openspec list --json` output.

How does delta spec synchronization work when finalizing an OpenSpec workflow change?

Delta spec synchronization detects specs under `openspec/changes/<name>/specs/`, compares them to corresponding main specs, presents a combined diff summary, and optionally performs the sync before the archiving directory move executes.

What limitations exist when moving an OpenSpec change directory into the archive?

Limitations of moving an OpenSpec change directory include the operation failing if the target archive path already exists and the strict requirement to move the whole directory to preserve the `.openspec.yaml` configuration file.