openspec-archive-change

Archive completed openspec changes into date-stamped folders after verification.

1|Updated Feb 22, 2026

Search Tags:#automation #workflow #archive #openspec #change-management #artifact-status #delta-specs

Ready to run

npx skills add https://github.com/SiddharthChillale/cloud-operations-reasoning-agent --skill openspec-archive-change-siddharthchillale

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/SiddharthChillale/cloud-operations-reasoning-agent/tree/main/.opencode/skills/openspec-archive-change
Command: npx skills add https://github.com/SiddharthChillale/cloud-operations-reasoning-agent --skill openspec-archive-change-siddharthchillale

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archive a completed change in the experimental workflow to finalize work, preserve provenance, and keep a clean history for audits.

Core Features & Use Cases

Guides users to select an active, unarchived change, verifies artifact and task completion, optionally performs delta-spec synchronization, and moves the change into a date-stamped archive folder for traceability.
Prompts for confirmation when needed and preserves relevant metadata for discovery.
Supports re-running the archiving process for recovery and audit scenarios.

Quick Start

Provide the change name to archive and let CORA handle the rest.

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

To archive completed openspec changes safely, select an active unarchived change, verify artifact and task completion, optionally sync delta-specs, and move the change into a date-stamped archive folder for traceability.

What is the best way to finalize and preserve provenance for change management artifacts?▼

Archiving completed changes finalizes work, preserves provenance, and keeps a clean history for audits by moving verified artifacts into a date-stamped archive directory.

Do I need the openspec CLI installed to move delta-specs to the archive folder?▼

Yes, archiving openspec changes requires the openspec CLI to be installed, read/write access to the openspec/changes directory, and system date access for archive naming.

Can I re-run the openspec change archiving process for audit recovery scenarios?▼

Yes, you can re-run the archiving process to recover and audit scenarios, prompting for confirmation when needed while preserving relevant metadata for discovery.

Why does openspec archive change verification check for artifact and task completion?▼

Artifact and task completion verification ensures that only fully finished openspec changes are moved to the date-stamped archive, preventing incomplete work from being finalized prematurely.

When do I need to sync delta-specs before moving changes to the archive directory?▼

Delta-spec synchronization is an optional step performed during the archiving process to ensure all incremental specification changes are synced before the final move to the archive folder.