skills.rest
kunish
kunishCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

openspec-archive-change

Archives completed changes to keep your project's spec history clean and organized.

Updated Mar 4, 2026
Search Tags:#automation#workflow#archive#openspec#change-management#artifact-status#delta-specs
One-click install
npx skills add https://github.com/kunish/muon --skill openspec-archive-change-kunish
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/kunish/muon/tree/main/.github/skills/openspec-archive-change
Command: npx skills add https://github.com/kunish/muon --skill openspec-archive-change-kunish

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archive a completed change in the experimental workflow.

Core Features & Use Cases

  • Automates the archival process with prompts for change selection, artifact and task status checks, delta-spec assessment, and a safe archive path.
  • Preserves essential metadata (e.g., .openspec.yaml) during archiving and provides a clear summary of results.
  • Supports configurable archive naming with date stamps and handles existing targets gracefully.

Quick Start

Provide the change name and follow the prompts to archive the change.

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 changes in an openspec workflow?▼

To archive completed openspec changes, you provide the change name and the skill applies artifact and task status checks, performs a delta-spec assessment, and safely moves files to openspec/changes/archive/YYYY-MM-DD-<name>.

What is the best way to automate change archiving while preserving metadata?▼

Automating change archiving is handled by enforcing change-name prompts and preserving essential metadata like .openspec.yaml during the file transfer to the dated archive directory.

Does the openspec archive process check for target conflicts before moving files?▼

Yes, the openspec archive process ensures no target conflicts exist before archiving, handling existing targets gracefully and providing a clear summary of the final archival results.

How do delta-specs affect the process to archive completed changes?▼

Delta-specs are assessed during the change archiving process to verify that all experimental workflow modifications are finalized and validated before the artifacts are safely moved.

Why do I need to check artifact and task statuses before archiving a change?▼

Checking artifact and task statuses is required before archiving a change to enforce guardrails, ensuring the implementation is fully completed and preventing premature archival of active workflow items.

Related Skills

Explore More Software Engineering Skills→
epamepam
503

openspec-archive-change

Validate and archive completed Openspec workflow changes while preserving configuration files.

Official
Advanced
rock-hurock-hu

openspec-archive-change

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

Community
Advanced
nuitsjpnuitsjp
1

openspec-ff-change

Automate artifact creation for OpenSpec changes using the openspec CLI.

Community
Advanced
jankneumannjankneumann
4

openspec-bulk-archive-change

Archive multiple completed OpenSpec changes while detecting spec conflicts.

Community
Advanced