skills.rest
cogidoo
cogidooCOMMUNITY
Explore all skills by this author →
GitHub

openspec-archive-change

Archive completed OpenSpec changes with date-based naming after validation.

Updated Apr 25, 2026
Search Tags:#workflow#archive#openspec#artifact#change-management#delta-spec
One-click install
npx skills add https://github.com/cogidoo/sunchaser --skill openspec-archive-change-cogidoo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/cogidoo/sunchaser/tree/main/.opencode/skills/openspec-archive-change
Command: npx skills add https://github.com/cogidoo/sunchaser --skill openspec-archive-change-cogidoo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archives a completed OpenSpec change in the experimental workflow, enabling clean history and reproducible archiving after implementation.

Core Features & Use Cases

  • Change selection: prompts for the change name if not provided.
  • Artifact and task verification: checks completion status via openspec status and tasks.md.
  • Delta-spec sync assessment: compares delta specs with main specs when present and guides syncing decisions.
  • Safe archival: moves the change directory into an archive folder with date-based naming, preserving .openspec.yaml.
  • Summary reporting: outputs a concise completion summary including artifacts, tasks, and archive location.

Quick Start

Provide the change name or let the tool prompt you to select, then initiate the archive process.

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

To archive a completed OpenSpec change, you provide the change name or let the tool prompt you to select one, then it validates artifacts and tasks before safely moving the directory into an archive folder with date-based naming.

What is the process for verifying OpenSpec artifacts and tasks before archiving?▼

The archiving process verifies completion status by checking OpenSpec status outputs and tasks.md, ensuring all artifacts and tasks are properly finalized before moving the change directory into the archive.

How do I sync delta specs with main specs during OpenSpec change management?▼

When delta specs are present, the archiving workflow compares them with main specs and guides syncing decisions to ensure spec consistency before finalizing the change archive.

Can I use OpenSpec archiving without manually specifying the change name?▼

Yes, you can initiate archiving without specifying the change name, and the tool will prompt you to select the appropriate completed change from the available options in your OpenSpec project.

What does OpenSpec archival do with the .openspec.yaml configuration file?▼

OpenSpec archival preserves the .openspec.yaml configuration file during the archival process, moving the entire change directory into the archive folder while maintaining its original configuration structure.

Does OpenSpec archiving provide a summary of the archived change?▼

Yes, the archiving process outputs a concise completion summary that includes the verified artifacts, checked tasks, and the final archive location with date-based naming for reproducible history.

Related Skills

Explore More Software Engineering Skills→
llama-farmllama-farm
2

openspec-verify-change

Verify codebase implementations against delta specifications and change artifacts.

Official
Advanced
rock-hurock-hu

openspec-archive-change

Archive completed openspec changes into dated paths after validating artifacts and tasks.

Community
Advanced
rock-hurock-hu

openspec-sync-specs

Merge delta specifications into main OpenSpec repository specs.

Community
Intermediate
DraculaboDraculabo
2.0k

openspec-archive-change

Archive completed OpenSpec changes with artifact checks and date-based naming.

Community
Advanced