openspec-archive-change

Archive a completed OpenSpec change and optionally sync delta specs.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/bgzbgz/show-time --skill openspec-archive-change-bgzbgz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/bgzbgz/show-time/tree/main/.claude/skills/openspec-archive-change
Command: npx skills add https://github.com/bgzbgz/show-time --skill openspec-archive-change-bgzbgz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archive a completed change in the experimental workflow to keep the active workspace clean and maintain an auditable history of changes.

Core Features & Use Cases

  • Archive completed OpenSpec changes into a structured archive directory, preserving metadata and notes.
  • Validate artifact and task completion, assess delta specs, and optionally sync specs before finalizing the archive.
  • Produce a concise summary post-archive and preserve the original changes directory with its .openspec.yaml.

Quick Start

Provide the change name to archive, or let the system prompt you to select one, and follow the prompts to complete the archive.

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 keep my workspace clean?

To archive completed OpenSpec changes, provide the change name and the system validates artifact and task completion before moving it to a structured archive directory. This preserves metadata and notes while keeping your active workspace clean.

What does it mean to sync delta specs during change management archiving?

Syncing delta specs during change management archiving means the system assesses pending specification changes and optionally integrates them before finalizing the archive. This ensures your OpenSpec repository reflects the completed modifications accurately.

Can I use OpenSpec archiving to validate if all tasks in a workflow are completed?

Yes, OpenSpec archiving performs required validations to check artifact and task completion before allowing the archive process to finish. This ensures only fully completed changes are moved to the archive directory.

How do I maintain an auditable history of OpenSpec changes?

You maintain an auditable history of OpenSpec changes by archiving completed modifications into a structured directory. The archive preserves the original changes directory and its .openspec.yaml file, providing a reliable audit trail.

What happens to the .openspec.yaml file when a change is archived?

When a change is archived, the .openspec.yaml file is preserved within the structured archive directory. The system moves the original changes directory intact, ensuring metadata and notes remain accessible for future reference.

Are there any limitations when archiving incomplete OpenSpec changes?

Archiving incomplete OpenSpec changes is limited by required validations that check for artifact and task completion. If these validations fail, the change cannot be finalized and moved to the archive directory until all requirements are met.