openspec-archive-change

Archive completed OpenSpec changes into date-stamped archive folders.

1|Updated Feb 4, 2026
One-click install
npx skills add https://github.com/oinani0721/canvas-learning-system --skill openspec-archive-change-oinani0721
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/oinani0721/canvas-learning-system/tree/main/.claude/skills/openspec-archive-change
Command: npx skills add https://github.com/oinani0721/canvas-learning-system --skill openspec-archive-change-oinani0721

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archive completed OpenSpec changes to keep a clean, auditable history of workflow modifications.

Core Features & Use Cases

  • Safe archival: moves finished changes into an organized archive folder with a date-stamped path
  • Pre-archive checks: validates artifact and task completion, and optional delta-spec synchronization
  • Audit-ready: preserves .openspec.yaml within archived changes for traceability

Quick Start

Archive a completed change by selecting it and running the archive flow with the OpenSpec CLI.

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 maintain an auditable history?▼

To archive completed OpenSpec changes, select the change and run the archive flow. It validates artifact and task completion, optionally syncs delta specs, and moves the change to openspec/changes/archive/YYYY-MM-DD-<name>.

What does OpenSpec archive validation check before moving a change?▼

OpenSpec archive validation checks that all artifacts and tasks are completed before moving the change. It optionally syncs delta specs and preserves .openspec.yaml to enforce preconditions and maintain a safe audit trail.

Does the OpenSpec archive flow work with delta-spec workflows?▼

Yes, the OpenSpec archive flow applies to both interactive and delta-spec workflows. It optionally syncs delta specs before moving the change into the archive folder to preserve a clean history.

Why does OpenSpec preserve .openspec.yaml when archiving changes?▼

OpenSpec preserves .openspec.yaml within archived changes to maintain traceability and an audit-ready history. This ensures the archived change retains its original configuration and metadata.

What is the best way to keep OpenSpec change history clean and audit-ready?▼

The best way to keep OpenSpec change history clean is to archive completed changes into a date-stamped folder. This moves finished changes to openspec/changes/archive/YYYY-MM-DD-<name> while preserving configuration files.