openspec-archive-change

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

2|Updated Feb 19, 2026

Search Tags:#workflow #archive #openspec #change-management #artifact-status #spec-delta

Ready to run

npx skills add https://github.com/llama-farm/demofly-claude --skill openspec-archive-change-llama-farm

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/llama-farm/demofly-claude/tree/main/.claude/skills/openspec-archive-change
Command: npx skills add https://github.com/llama-farm/demofly-claude --skill openspec-archive-change-llama-farm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archive a completed change in the experimental workflow.

Core Features & Use Cases

Validates artifact completion via openspec status to ensure only finalized changes are archived.
Compares delta specs against main specs when present to surface changes before archival.
Creates an archive directory and moves the change with its metadata, preserving .openspec.yaml and related artifacts.

Quick Start

Run the archive operation for a specific change name to finalize and move the change into 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 changes in OpenSpec without losing metadata?▼

To archive completed changes safely, the workflow validates completion via openspec status, creates an archive directory, and moves the change while preserving its .openspec.yaml and related artifacts.

Does OpenSpec check if a change is ready before moving it to the archive?▼

Yes, OpenSpec checks readiness by validating artifact completion via openspec status, ensuring that only finalized changes are moved into the archive directory with their metadata intact.

How do I compare delta specs against main specs before archiving a change?▼

Before archiving a change, the workflow compares delta specs against main specs when present to surface modifications, then prompts for user decisions to finalize the archival process.

What is the best way to manage change archival in an experimental workflow?▼

The best way to manage change archival is using a guarded process that validates completion, compares spec deltas, and moves finalized changes into an archive directory to preserve metadata.

Can I synchronize delta specs when finalizing changes in OpenSpec?▼

Yes, you can synchronize delta specs during the archival process; the workflow compares delta specs against main specs when present and prompts for decisions before moving the change.

Why does OpenSpec prompt for user decisions during the change archival process?▼

OpenSpec prompts for user decisions to confirm changes after comparing delta specs against main specs, ensuring developers and operators explicitly verify modifications before finalizing the archive.