openspec-archive-change

Name: openspec-archive-change
Availability: InStock
Author: paradox123

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

Updated Jan 23, 2026

Search Tags:#automation #workflow #cli #archive #openspec #change

Ready to run

npx skills add https://github.com/paradox123/shared-ai-docs --skill openspec-archive-change-paradox123

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/paradox123/shared-ai-docs/tree/main/.codex/skills/openspec-archive-change
Command: npx skills add https://github.com/paradox123/shared-ai-docs --skill openspec-archive-change-paradox123

SYSTEM DOCUMENTATION & REQUIREMENTS

## What problem does it solve? Archive a completed change in the experimental workflow, ensuring proper lifecycle handling, auditability, and easy retrieval.

## Core Features & Use Cases

Finalizes and archives completed changes after implementation.
Creates a date-stamped archive entry under openspec/changes/archive/.
Supports optional delta-spec synchronization and artifact/status checks before archiving.

### Quick Start Archive the change by validating artifacts and moving it to the archive directory.

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 finalize their lifecycle?▼

Archiving completed OpenSpec changes involves running artifact and delta-spec checks before moving the directory to openspec/changes/archive/YYYY-MM-DD-<name>, preserving the .openspec.yaml file to finalize the lifecycle.

What is the process for preserving OpenSpec change history after implementation?▼

Preserving OpenSpec change history requires archiving completed changes into a date-stamped directory under openspec/changes/archive/, which finalizes the lifecycle and enables easy retrieval of past artifacts.

Can I sync delta-specs before moving an OpenSpec change to the archive?▼

Yes, the archiving workflow supports optional delta-spec synchronization. It prompts you to sync delta-specs during artifact checks before moving the completed change into the archive directory.

Does archiving an OpenSpec change preserve the .openspec.yaml configuration file?▼

Yes, archiving an OpenSpec change preserves the .openspec.yaml configuration file. The workflow functionally ensures this file remains intact when moving the change into the date-stamped archive directory.

What is the best way to automate completed change archiving in a CLI workflow?▼

Automating completed change archiving in a CLI workflow is done via a single command that validates artifacts, handles delta-spec syncing, and moves the OpenSpec change to the archive directory.

When do I need to run artifact checks before archiving an OpenSpec change?▼

Artifact checks must run before archiving an OpenSpec change to validate required files and prevent incomplete changes from being moved into the archive directory.