openspec-archive-change

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

Archive completed experimental changes into date-stamped directories with metadata.

Updated Mar 7, 2026

Search Tags:#workflow #validation #audit #archive #openspec #change-management

Ready to run

npx skills add https://github.com/YangYuS8/blog --skill openspec-archive-change-yangyus8

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/YangYuS8/blog/tree/main/.opencode/skills/openspec-archive-change
Command: npx skills add https://github.com/YangYuS8/blog --skill openspec-archive-change-yangyus8

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archive completed changes from experimental workflows to preserve a clean, auditable history.

Core Features & Use Cases

Guided archiving: Move finalized changes to a date-stamped archive with preserved metadata.
Validation & safety: Includes optional checks and prompts to ensure consistency before archiving.
Audit-ready history: Keeps artifacts and metadata for future review and recovery.

Quick Start

Archive a completed change by running the openspec archive command and specifying the change name.

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

You can archive completed workflow changes by running the openspec archive command and specifying the change name, which moves finalized changes to a date-stamped archive with preserved metadata.

Why do I need to validate outputs before archiving a change?▼

Validating outputs before archiving ensures consistency across your workflow by applying safety checks and prompts, confirming that finalized work is accurate before being permanently relocated to the archive.

What is the best way to maintain an auditable history of experimental workflow changes?▼

The best way to maintain an auditable history is to move finalized changes into a date-stamped archive, which retains necessary artifacts and metadata for future review and recovery.

Can I synchronize specs when archiving completed changes?▼

Yes, you can synchronize specs during the archiving process. This guided operation supports optional spec synchronization to ensure your documentation matches the finalized workflow changes.

Does archiving experimental changes delete the original metadata?▼

Archiving experimental changes does not delete original metadata. The process safely relocates files to a date-stamped archive while retaining necessary metadata to keep artifacts audit-ready.