openspec-archive

Archive deployed OpenSpec changes and synchronize associated specification files.

1|Updated Jan 31, 2026

Search Tags:#documentation #deployment #specification #cli #archive #openspec

Ready to run

npx skills add https://github.com/charly-vibes/wai --skill openspec-archive-charly-vibes

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-archive
Source: https://github.com/charly-vibes/wai/tree/main/.agents/skills/openspec-archive
Command: npx skills add https://github.com/charly-vibes/wai --skill openspec-archive-charly-vibes

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the process of archiving a deployed OpenSpec change and ensures that associated specifications are correctly updated, streamlining the release and documentation lifecycle.

Core Features & Use Cases

Automated Archiving: Moves completed OpenSpec changes to an archive state.
Spec Synchronization: Updates relevant specification files to reflect the archived change.
Use Case: After successfully deploying a new API endpoint defined by an OpenSpec change, use this Skill to formally archive the change and update the API documentation.

Quick Start

Archive the OpenSpec change with ID 'change-12345'.

Frequently Asked Questions about openspec-archive

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I archive OpenSpec changes after deployment?▼

To archive OpenSpec changes after deployment, you can use a Skill that moves completed changes to an archive state and synchronizes specification files. It requires the OpenSpec CLI to list, validate, and archive the changes automatically.

What is OpenSpec specification synchronization?▼

OpenSpec specification synchronization is the process of updating relevant spec files to reflect archived changes. This ensures documentation accuracy post-deployment by keeping deployed changes and their associated specifications aligned.

How do I update API documentation after deploying an OpenSpec change?▼

You update API documentation after deploying an OpenSpec change by archiving the change. This action automatically synchronizes the associated specification files to reflect the newly deployed endpoint or modification.

Do I need the OpenSpec CLI to archive changes?▼

Yes, you need the OpenSpec CLI to archive changes. The CLI is required to list, validate, and archive changes, ensuring the associated specification files are correctly synchronized during the release lifecycle.

When should I archive an OpenSpec change?▼

You should archive an OpenSpec change after successfully deploying the associated modification. This manages the change lifecycle by formally moving the completed change to an archive state and updating the documentation.

What's the best way to manage the OpenSpec change lifecycle?▼

The best way to manage the OpenSpec change lifecycle is by archiving deployed changes and updating specs. This streamlines the release process by automating the transition to an archive state and synchronizing documentation.