openspec-archive-change

Archive completed openspec changes into date-stamped folders after validating artifacts and tasks.

Updated Jan 23, 2026

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

Ready to run

npx skills add https://github.com/hossam7amdy/easy-auth --skill openspec-archive-change-hossam7amdy

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/hossam7amdy/easy-auth/tree/main/.agent/skills/openspec-archive-change
Command: npx skills add https://github.com/hossam7amdy/easy-auth --skill openspec-archive-change-hossam7amdy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps engineering teams finalize and organize change work by archiving completed experimental changes in the openspec workflow, preserving history, artifacts, and configuration for future reference.

Core Features & Use Cases

Change selection & validation: Prompt for the change name if not provided and verify artifact and task completion status.
Delta-spec synchronization: Evaluate any delta specs against main specs and optionally perform a sync before archiving.
Archive & traceability: Move the change into a date-stamped archive folder while preserving the .openspec.yaml configuration, enabling easy rollback and auditing.

Quick Start

Supply a change name when prompted, or ask to list active changes. The tool will validate artifacts and tasks, assess delta specs, optionally perform a sync, and archive the change to openspec/changes/archive/YYYY-MM-DD-<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 in openspec?▼

To archive completed workflow changes in openspec, you provide a change name, and the tool validates artifact completion, checks task status, assesses delta-spec synchronization, and moves the directory to a date-stamped archive folder. This preserves history and configuration for future reference.

What is delta-spec synchronization before archiving an openspec change?▼

Delta-spec synchronization is the process of evaluating experimental delta specs against main specs before archiving. The tool assesses these differences and optionally performs a sync to ensure main specs reflect completed work before the change directory is moved.

Can I rollback an archived change if I need to access the artifacts again?▼

Yes, rollback and auditing are possible because archiving preserves the .openspec.yaml configuration and related artifacts. The change is moved into a date-stamped archive path rather than deleted, maintaining full traceability for future reference.

Do I need the openspec CLI to archive experimental changes?▼

Yes, you need the openspec CLI installed to archive experimental changes. The Skill requires the CLI to perform checks against openspec/status, openspec/changes, and related specs during the validation and archiving process.

Why does my openspec change archive fail validation?▼

Archive validation fails when artifact completion or task status checks are not met. The tool verifies these prerequisites before moving the change directory, ensuring only fully completed work with synchronized delta specs is archived.