openspec-archive-change

Name: openspec-archive-change
Availability: InStock
Author: open-platform-model

Archive completed OpenSpec changes with metadata preservation.

Updated Dec 8, 2025

Search Tags:#workflow #artifacts #archive #openspec #change #delta-specs

Ready to run

npx skills add https://github.com/open-platform-model/cli --skill openspec-archive-change-open-platform-model

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/open-platform-model/cli/tree/main/.opencode/skills/openspec-archive-change
Command: npx skills add https://github.com/open-platform-model/cli --skill openspec-archive-change-open-platform-model

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.

Core Features & Use Cases

Archive completed OpenSpec changes to keep the workspace organized and prevent rework.
Validate artifact and task completion, assess delta-spec synchronization, and safely move the change into an archive directory, preserving metadata.
Use-case: After finishing a change, you archive it to stable storage and later reference it for audits or rollback.

Quick Start

Run the archive workflow to move the change directory into openspec/changes/archive with a dated name and generate a summary.

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

After finishing a change implementation, you archive it to keep the workspace organized and prevent rework. The workflow validates completion via openspec status, moves the change directory to openspec/changes/archive with a dated name, and generates a summary.

What happens to delta-specs when archiving an OpenSpec change?▼

When archiving a change, the workflow assesses delta-spec synchronization before moving the directory. This check ensures delta-specs are properly aligned and metadata is preserved during the safe archival process.

When should I archive an OpenSpec change in the workflow?▼

You should archive a change when implementation is complete and you want to finalize it. Archiving moves the change to stable storage, keeping the workspace organized and allowing later reference for audits or rollback.

Does archiving OpenSpec changes validate task and artifact completion?▼

Yes, the workflow validates artifact and task completion by checking openspec status. It prompts for change selection when needed and ensures tasks are complete before safely moving the change to the archive directory.

Can I reference archived OpenSpec changes for audits or rollback?▼

Yes, archived changes can be referenced for audits or rollback. The process moves the change directory into openspec/changes/archive with a dated name and generates a summary while preserving metadata for future access.