openspec-archive-change

Archive a completed OpenSpec change after verifying artifact and task completion.

Updated Aug 23, 2026

Search Tags:#automation #workflow #validation #archive #openspec #changes #delta-specs

Ready to run

npx skills add https://github.com/anaclumos/verifidia --skill openspec-archive-change-anaclumos

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/anaclumos/verifidia/tree/main/.opencode/skills/openspec-archive-change
Command: npx skills add https://github.com/anaclumos/verifidia --skill openspec-archive-change-anaclumos

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archive a completed OpenSpec change to prevent rework and maintain a clean change history in a structured archive.

Core Features & Use Cases

Validation prompts: Ensure a change is eligible for archiving by confirming artifact and task completion and delta-spec status.
Delta-spec awareness: Detect and compare delta specs with main specs to determine sync needs and offer appropriate actions.
Date-stamped archiving: Move the change to openspec/changes/archive/YYYY-MM-DD-<name> while preserving metadata.
Summary reporting: Provide a clear final summary including schema used, archive location, and any warnings.

Quick Start

Tell me to archive change 'CHANGE-NAME' once work is complete.

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 to keep the history clean?▼

Archive completed OpenSpec changes by moving the change folder to openspec/changes/archive/YYYY-MM-DD-<name>. The workflow verifies artifact and task completion and checks delta-spec sync status before safely moving the change and preserving metadata.

What happens to delta specs when archiving an OpenSpec change?▼

When archiving an OpenSpec change, the workflow detects delta specs and compares them against main specs to determine sync needs. It then offers appropriate synchronization actions before moving the change to the date-stamped archive directory.

Can I archive an OpenSpec change if tasks are not fully completed?▼

No, archiving an OpenSpec change requires confirming artifact and task completion first. Validation prompts check delta-spec status and completion guardrails to ensure the change is fully eligible before proceeding to the archive step.

How do I get a summary report after archiving an OpenSpec change?▼

After archiving an OpenSpec change, the workflow provides a clear final summary. This summary includes the schema used, the exact archive location, and any warnings encountered during the validation and moving process.