openspec-archive-change

Archive completed OpenSpec changes with date-prefixed directory moves.

43|1|Updated Mar 12, 2026

Search Tags:#automation #workflow #artifacts #archive #openspec #change #delta-specs

Ready to run

npx skills add https://github.com/liyown/XHSSpec --skill openspec-archive-change-liyown

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/liyown/XHSSpec/tree/main/.claude/skills/openspec-archive-change
Command: npx skills add https://github.com/liyown/XHSSpec --skill openspec-archive-change-liyown

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archive a completed change in the experimental OpenSpec workflow, ensuring the change is finalized and stored for future reference and reuse.

Core Features & Use Cases

Archives a completed change after verification of artifacts and tasks.
Moves the change directory to an archive location with a date-prefixed name.
Optionally prompts for delta-spec synchronization, preserves metadata, and reports a clear summary.

Quick Start

Run openspec to archive a completed change after implementation is verified.

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 a completed change in OpenSpec?▼

To archive a completed OpenSpec change, run the openspec command to verify artifacts and tasks are complete, then move the change directory to an archive path with a date prefix. The process checks status via openspec status and delta specs before finalizing the archival.

What happens if I try to archive an OpenSpec change with incomplete tasks?▼

When archiving an OpenSpec change with incomplete tasks or artifacts, the process reports warnings instead of finalizing successfully. It verifies completion by checking openspec status and delta specs in the changes directory, ensuring only verified changes get archived.

When do I need to archive delta specs in OpenSpec workflows?▼

You need to archive delta specs in OpenSpec workflows after implementation is verified and all tasks are complete. This ensures finalized changes are stored with metadata in a date-prefixed archive location for future reference and reuse.

Does archiving a change in OpenSpec synchronize delta specs automatically?▼

Archiving a change in OpenSpec optionally prompts for delta-spec synchronization. The process reports whether specs were synced and preserves necessary metadata, returning a clear summary indicating successful sync status or warnings for incomplete items.

Can I use the OpenSpec CLI to verify artifacts before archiving a change?▼

Yes, the OpenSpec CLI checks status via openspec status and verifies delta specs in the openspec/changes directory before archiving. It prompts for user confirmation when needed, ensuring artifacts and tasks are complete prior to moving the change directory.