openspec-archive-change

Archive completed OpenSpec changes with date-based naming and validation.

Updated Feb 12, 2026

Search Tags:#workflow #archive #openspec #version-control #change-management #artifact-status #delta-specs

Ready to run

npx skills add https://github.com/martinsson/checkin-automation --skill openspec-archive-change-martinsson

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archive completed OpenSpec changes to keep the workspace tidy and preserve a traceable history of finalized work, including the associated artifacts and delta specifications.

Core Features & Use Cases

Artifact and task status checks before archiving to ensure completed work.
Delta-spec alignment assessment to determine if a sync is needed before archiving.
Safe archival with date-based naming and preservation of metadata and configuration files.

Quick Start

Provide the change name when prompted and follow the prompts to archive after all artifacts and tasks are 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 project history clean?▼

To archive completed OpenSpec changes safely, you provide the change name and follow the prompts to execute date-based archiving, which preserves metadata and keeps your workspace tidy. The process includes artifact and task status checks before moving the files.

When should I archive delta specs in my change management workflow?▼

You should archive delta specs when all associated artifacts and tasks are finished and you need to preserve a traceable history of finalized work. The archiving mechanism assesses delta-spec alignment to determine if synchronization is needed before moving the files.

Can I archive OpenSpec artifacts if task statuses are not fully complete?▼

Archiving OpenSpec artifacts requires completed task statuses, as the process performs artifact and status checks before initiating the date-based archival. You must ensure all associated work is finalized to prevent loss of metadata during the workspace cleanup.

Does the OpenSpec archive process support delta-spec synchronization before moving files?▼

Yes, the OpenSpec archive process supports optional delta-spec synchronization by performing a delta-spec alignment assessment. This comparison determines if a sync is required before the safe archival with date-based naming and metadata preservation occurs.

What is the best way to prevent metadata loss when archiving version-control changes?▼

The best way to prevent metadata loss during archiving is to use an archive validation process that preserves configuration files and associated artifacts. This ensures finalized work remains traceable and intact within your project history after the delta specs are moved.

Why do I need to provide the change name when archiving OpenSpec work?▼

Providing the change name specifies exactly which completed OpenSpec artifacts and delta specs to archive. This ensures the date-based archiving correctly targets the finalized work, preserving the right metadata and configuration files while keeping the workspace tidy.