openspec-archive-change

Archives completed OpenSpec changes with date-stamped directories and artifact validation.

Updated Feb 4, 2026

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

Ready to run

npx skills add https://github.com/memorysaver/agentpit-gg --skill openspec-archive-change

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/memorysaver/agentpit-gg/tree/main/.opencode/skills/openspec-archive-change
Command: npx skills add https://github.com/memorysaver/agentpit-gg --skill openspec-archive-change

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archives a completed OpenSpec change to preserve its final state and provenance after implementation.

Core Features & Use Cases

Archiving completed changes to openspec/changes/archive with date-stamped directories.
Optional delta-spec synchronization assessment before archiving to ensure consistency with main specs.
Status validation of artifacts via openspec status to guarantee completeness before archiving.

Quick Start

Run the archive action after a change is implemented. If a change name is not provided, the tool will prompt for it, verify artifact completion, assess delta specs, perform the archive, and present a final summary.

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 OpenSpec change with date-stamped provenance?▼

Archive a completed OpenSpec change by running the archive action after implementation. The skill validates artifact completion via openspec status, assesses delta-spec synchronization if present, and stores the change under openspec/changes/archive/YYYY-MM-DD-<name>, preserving the .openspec.yaml file for full provenance.

What does openspec status validation do before archiving a change?▼

openspec status validation checks that all artifacts in your change are complete before archiving proceeds. This guarantees you're only archiving finalized work and prevents incomplete changes from being stored in the archive.

Do I need to manually sync delta specs before archiving an OpenSpec change?▼

The archive skill includes optional delta-spec synchronization assessment built in. It automatically compares delta specs against main specs when present, so you don't need to manage that manually—the skill surfaces any inconsistencies during the archive process.

Can I archive an OpenSpec change without providing a change name?▼

Yes. If you don't provide a change name, the archive action prompts you for it interactively, then proceeds with artifact validation and archiving. The workflow handles input collection automatically.

What happens to the original .openspec.yaml file when I archive a change?▼

The original .openspec.yaml is preserved during archiving. The skill maintains the complete state and configuration of your change in the archive, ensuring full traceability of what was implemented.

Is the openspec CLI required to use the archive workflow?▼

Yes, the archive skill requires the openspec CLI to function. It depends on openspec status for artifact validation and openspec archive commands to store changes in date-stamped archive directories.