openspec-archive-change

Archive completed OpenSpec changes to openspec/changes/archive after deployment.

Updated Jan 29, 2026

Search Tags:#workflow #deployment #archive #openspec #specs #change

Ready to run

npx skills add https://github.com/hongquandev/OpenSpec-VI --skill openspec-archive-change-hongquandev

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/hongquandev/OpenSpec-VI/tree/main/.agent/skills/openspec-archive-change
Command: npx skills add https://github.com/hongquandev/OpenSpec-VI --skill openspec-archive-change-hongquandev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archives a completed OpenSpec change after a deployment to preserve state, ensure traceability, and provide a clear record of what was implemented and stored.

Core Features & Use Cases

Validates that all artifacts are completed before archiving and prompts for confirmation if any artifacts are not done.
Verifies task completion and delta-spec alignment, offering guidance to synchronize specs when needed.
Creates a dedicated archive directory openspec/changes/archive, moves the change directory there, and preserves the .openspec.yaml metadata for traceability.

Quick Start

Archive a completed OpenSpec change after deployment to openspec/changes/archive after verifying artifacts, tasks, and delta specs.

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 deployment?▼

To archive OpenSpec changes after deployment, the workflow validates all artifacts and tasks, optionally synchronizes delta specs, and moves the change directory to openspec/changes/archive while preserving .openspec.yaml metadata for traceability.

What happens if some artifacts are not completed before archiving an OpenSpec change?▼

If artifacts are not completed before archiving an OpenSpec change, the process enforces end-to-end checks and prompts for confirmation, ensuring no incomplete work is archived without explicit approval.

When should I archive specs in a deployment workflow?▼

You should archive specs in a deployment workflow immediately after successful deployment to preserve state, ensure traceability, and maintain a clear record of what was implemented before starting new changes.

How do I synchronize delta specs during the change archival process?▼

To synchronize delta specs during change archival, the process verifies task completion and delta-spec alignment, offering guidance to synchronize specs when misalignment is detected before moving to the archive directory.

Does the archival process preserve OpenSpec metadata for traceability?▼

Yes, the archival process preserves the .openspec.yaml metadata by moving the entire change directory to openspec/changes/archive, maintaining configuration integrity for traceability.

What is the best way to manage change archival governance across projects?▼

The best way to manage change archival governance is applying an automated workflow that enforces artifact validation, task verification, and delta-spec alignment before safely storing changes in a dedicated archive directory.