openspec-archive-change

Archive completed OpenSpec changes with validation and dated folder output.

3|1|Updated Feb 1, 2026
One-click install
npx skills add https://github.com/moltbook-experiments/glasshouse-protocol --skill openspec-archive-change-moltbook-experiments
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/moltbook-experiments/glasshouse-protocol/tree/main/.github/skills/openspec-archive-change
Command: npx skills add https://github.com/moltbook-experiments/glasshouse-protocol --skill openspec-archive-change-moltbook-experiments

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archiving completed OpenSpec changes to finalize implementations and preserve a verifiable record for audit and rollback.

Core Features & Use Cases

  • Prompted change selection to ensure the user confirms which change to archive.
  • Artifact and task status checks to catch incomplete work before archiving.
  • Optional delta-spec synchronization to align archived changes with main specs when present.
  • Safe archiving to openspec/changes/archive with a dated folder and preserved metadata.

Quick Start

Run the archive command for the selected change using 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 finalize an implementation?

To archive OpenSpec changes, prompt for change selection, verify artifact and task statuses, optionally sync delta-specs, and move the change to openspec/changes/archive with a dated folder name for a verifiable record.

What does delta-spec synchronization do when archiving an OpenSpec change?

Delta-spec synchronization aligns archived OpenSpec changes with main specs when present. It ensures the archived record matches the finalized implementation before safe archival.

Can I archive an OpenSpec change if artifact and task checks are incomplete?

No, artifact and task status checks catch incomplete work before archiving. You must resolve pending tasks and verify all artifacts to finalize the implementation and retain a verifiable record.

When should I use an OpenSpec change archive workflow?

Use an OpenSpec change archive workflow after completing an implementation to finalize it and preserve a verifiable record for audit and rollback. It enforces change selection and artifact checks.

What is the best way to retain a verifiable record of completed OpenSpec changes?

The best way to retain a verifiable record is safe archiving to openspec/changes/archive with a dated folder name. This preserves metadata and optionally syncs delta-specs for audit and rollback.