openspec-archive-change

Name: openspec-archive-change
Availability: InStock
Author: mazhewitt

Archives completed changes from the experimental workflow after implementation.

Updated Feb 15, 2026

Search Tags:#workflow #archive #openspec #change-management #artifact-tracking #spec-sync

Ready to run

npx skills add https://github.com/mazhewitt/budget-analyser --skill openspec-archive-change-mazhewitt

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/mazhewitt/budget-analyser/tree/main/.gemini/skills/openspec-archive-change
Command: npx skills add https://github.com/mazhewitt/budget-analyser --skill openspec-archive-change-mazhewitt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archive completed changes from the experimental workflow to keep repositories clean and ensure traceability of finalized work.

Core Features & Use Cases

Interactive change selection for archival
Artifact and task status verification before archiving
Delta-spec synchronization assessment and optional syncing
Preserves crucial configuration files during move and archives to openspec/changes/archive

Quick Start

Provide the change name to archive, and follow the prompts to select, verify status, and complete the archive.

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 while keeping setup files intact?▼

To archive completed OpenSpec changes, the Skill moves finalized work into a dated archive directory while explicitly preserving your crucial setup files. It enforces artifact and task completion checks before moving anything.

What happens if I try to archive an OpenSpec change with incomplete tasks?▼

Archiving incomplete OpenSpec changes is blocked by the Skill's artifact and task status verification. It uses openspec commands to check completion status and prevents the archive move if tasks remain unfinished.

Can I synchronize delta-specs when archiving completed changes?▼

Yes, delta-spec synchronization is assessed during the change archival process. The Skill evaluates your delta-specs and provides an optional syncing step before moving the change to the archive directory.

Do I need to specify the change name manually to use the archive workflow?▼

No, you do not need to specify the change name manually. If a change name is not provided, the Skill prompts you with interactive change selection to identify which completed change you want to archive.

What is the best way to keep repositories clean after finalizing experimental workflow changes?▼

Archiving completed experimental workflow changes is the best way to maintain repository cleanliness and ensure traceability. This Skill safely moves finalized work into openspec/changes/archive and returns a concise summary.

Why does the archiving process verify artifact and task status before moving files?▼

Verifying artifact and task status before archiving ensures that only fully completed changes are moved to the dated archive directory. This prevents traceability gaps and avoids archiving incomplete experimental workflow work.