openspec-archive-change

Archive completed OpenSpec changes with artifact status checks and spec synchronization.

6|Updated Feb 5, 2026

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

Ready to run

npx skills add https://github.com/jacobcy/vibe-coding-control-center --skill openspec-archive-change-jacobcy

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/jacobcy/vibe-coding-control-center/tree/main/.github/skills/openspec-archive-change
Command: npx skills add https://github.com/jacobcy/vibe-coding-control-center --skill openspec-archive-change-jacobcy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archive completed OpenSpec changes into an archival area after implementation to prevent clutter and enable long-term traceability.

Core Features & Use Cases

Validates artifact completion and task status before archiving to ensure only finished changes are retained.
Checks for delta specs and optionally syncs with main specs to keep archives aligned.
Archives the change into openspec/changes/archive/YYYY-MM-DD-<name> while preserving configuration files and providing a final status summary.

Quick Start

Execute the OpenSpec archive command for the chosen change to complete the archival process.

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 after implementation?▼

To archive completed OpenSpec changes, execute the archive command which validates artifact completion and task status, then moves the change into openspec/changes/archive/YYYY-MM-DD-<name> while preserving configuration files and reporting a final status summary.

What is the process for syncing delta specs during OpenSpec change archival?▼

Syncing delta specs during OpenSpec change archival involves checking for delta specs and optionally synchronizing them with main specs to keep archives aligned, ensuring completed changes are retained accurately.

When do I need to archive changes in an OpenSpec workflow?▼

You need to archive changes in an OpenSpec workflow after implementation is complete to prevent clutter and enable long-term traceability of finished changes.

Can I archive an OpenSpec change if artifact status checks are not completed?▼

No, you cannot archive an OpenSpec change if artifact status checks are not completed; the archival process coordinates artifact status checks and task completion to determine archivable changes.

What's the best way to manage OpenSpec artifact status before archiving?▼

The best way to manage OpenSpec artifact status before archiving is to ensure all tasks are completed and artifacts are validated, as the archive process checks these statuses to determine if a change is archivable.