openspec-archive-change

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

Updated Jul 26, 2025

Search Tags:#automation #workflow #archive #openspec #changes #delta-spec #artifact-status

Ready to run

npx skills add https://github.com/0serna/dotfiles --skill openspec-archive-change-0serna

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/0serna/dotfiles/tree/main/dotfiles/agents/skills/openspec-archive-change
Command: npx skills add https://github.com/0serna/dotfiles --skill openspec-archive-change-0serna

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archive completed changes in the OpenSpec workflow to finalize and store completed work.

Core Features & Use Cases

Coordinate selection of the change to archive, verify artifact status, and assess delta-spec sync state.
Move the change directory into an archive folder with a date-based naming convention.
Generate a concise summary report of the archive operation, including any warnings related to incomplete artifacts or tasks, and whether specs were synced.

Quick Start

Archive a finished change by invoking the tool and following the prompts to select a change, confirm artifact and task completion, optionally sync delta specs, and archive the change.

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 the OpenSpec workflow?▼

To archive completed OpenSpec changes, you select the finished change, verify artifact and task completion, optionally sync delta specs, and move the change directory into a date-based archive folder with a final summary report.

When should I archive an OpenSpec change instead of keeping it active?▼

You should archive an OpenSpec change when its implemented work is done, artifacts are completed, and verification is finished, meaning the change requires finalization and storage rather than active development.

What happens if artifacts or tasks are incomplete when archiving an OpenSpec change?▼

When archiving an OpenSpec change with incomplete artifacts or tasks, the process generates a concise summary report that includes specific warnings about the incomplete items while still finalizing the archive operation.

Does the OpenSpec archive process handle delta-spec synchronization automatically?▼

The OpenSpec archive process assesses delta-spec sync state and optionally performs syncing during the archival workflow, allowing you to confirm whether specs should be synced before moving the change directory to the archive.

How are archived OpenSpec changes named and stored?▼

Archived OpenSpec changes are stored by moving the change directory into an archive folder using a date-based naming convention, ensuring completed changes are finalized and organized chronologically for future reference.

What is the best way to finalize and store completed OpenSpec changes?▼

The best way to finalize completed OpenSpec changes is through a coordinated archive workflow that selects the change, checks artifact status, assesses delta-spec sync, and generates a summary report of the entire operation including any warnings.