openspec-archive-change

Archive completed OpenSpec changes with metadata preservation and delta-spec sync checks.

30|6|Updated Jan 26, 2026
One-click install
npx skills add https://github.com/tatargabor/wt-tools --skill openspec-archive-change-tatargabor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/tatargabor/wt-tools/tree/main/.claude/skills/openspec-archive-change
Command: npx skills add https://github.com/tatargabor/wt-tools --skill openspec-archive-change-tatargabor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archive a completed OpenSpec change by safely moving it to an archival location.

Core Features & Use Cases

  • Centralized archiving of completed changes with preservation of metadata and artifact state.
  • Automatic delta-spec synchronization assessment and optional syncing before archiving.
  • Safe relocation to openspec/changes/archive with a date-stamped folder name and retention of .openspec.yaml.

Quick Start

Archive a completed OpenSpec change by selecting the change and running the archive workflow to move the change into the archive folder.

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 completed OpenSpec changes safely?

OpenSpec change archiving safely relocates completed changes by moving them to openspec/changes/archive with a date-stamped folder name. It performs artifact completeness checks and preserves .openspec.yaml metadata for traceability before relocation.

What is delta-spec synchronization assessment in change management?

Delta-spec synchronization assessment is the process of comparing specs before archiving an OpenSpec change. The workflow evaluates delta-specs during the status check phase and optionally syncs them to ensure artifact completeness and consistency.

Does OpenSpec archiving preserve .openspec.yaml metadata?

Yes, OpenSpec archiving preserves .openspec.yaml metadata during the safe relocation process. The workflow retains this configuration file within the date-stamped archive folder to maintain full traceability of the completed change artifacts.

How do I check artifact completeness before finalizing OpenSpec changes?

You check artifact completeness by initiating the OpenSpec archive workflow, which automatically performs status checks on the selected change. It evaluates artifact state and compares delta-specs before allowing the safe relocation to the archive.

What is the best way to move completed OpenSpec changes to an archive folder?

The best way to move completed OpenSpec changes is using a dedicated archive workflow that automates safe relocation to openspec/changes/archive. It handles delta-spec synchronization, enforces completeness checks, and generates a concise summary of the archive.

Why does OpenSpec change archiving require status checks before relocation?

OpenSpec change archiving requires status checks to ensure artifact completeness and verify delta-spec synchronization before relocation. This prevents incomplete or out-of-sync changes from being safely moved to the openspec/changes/archive directory.