skills.rest
LuminairPrime
LuminairPrimeCOMMUNITY
Explore all skills by this author →
GitHub

openspec-archive-change

Archives completed changes in the OpenShift workflow with validation and spec synchronization.

Updated May 16, 2026
Search Tags:#CLI#archive#change management#OpenSpec#spec synchronization
One-click install
npx skills add https://github.com/LuminairPrime/skill-tree-chopper --skill openspec-archive-change-luminairprime
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/LuminairPrime/skill-tree-chopper/tree/main/.gemini/skills/openspec-archive-change
Command: npx skills add https://github.com/LuminairPrime/skill-tree-chopper --skill openspec-archive-change-luminairprime

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires openspec, and includes scripts (resource) components.

What problem does it solve?

Manages the archival of completed changes in the OpenSpec workflow, ensuring a clear separation of implemented changes and preserving the history for reference.

Core Features & Use Cases

  • Change Archival: Finalize and archive changes once they are implemented.
  • Status Checking: Validates completion status of artifacts and tasks.
  • Spec Synchronization: Optionally synchronize delta specs before archiving.
  • User Confirmation: Informs the user of incomplete steps and requests confirmation.

Quick Start

To archive a completed change, run 'archive_change' and follow the prompts to select the change to be archived.

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 OpenSpec workflow?▼

To archive completed changes in OpenSpec workflow, run the archive_change command and follow the prompts to select the specific change you want to finalize and archive for historical reference.

What happens if artifacts or tasks are incomplete when archiving changes in OpenSpec?▼

When archiving changes in OpenSpec, the system checks the completion status of artifacts and tasks. It informs you of incomplete steps and requests confirmation before proceeding with the archival process.

Can I synchronize delta specs before archiving changes in OpenSpec?▼

Yes, you can optionally synchronize delta specs before archiving changes in OpenSpec. This feature ensures your specifications are fully updated and finalized before the change is moved to the archive.

Do I need the OpenSpec CLI to manage change archival?▼

Yes, managing change archival requires the OpenSpec CLI and a working knowledge of the OpenSpec project structure to properly validate artifacts, synchronize delta specs, and finalize implemented changes.

Why does my OpenSpec change archival process require user confirmation?▼

The OpenSpec change archival process requires user confirmation to ensure you are informed of any incomplete steps or validation issues before finalizing the separation of implemented changes into the archive.

Related Skills

Explore More Software Engineering Skills→
kamansoftkamansoft

openspec-continue-change

Generate the next artifact in an OpenSpec change workflow.

Official
Intermediate
statick88statick88
1

sdd-archive

Merge delta specifications into main specs and archive completed change folders.

Community
Advanced
081595081595

openspec-continue-change

Create the next artifact in an OpenSpec change lifecycle.

Community
Intermediate
inspedralbesinspedralbes

openspec-bulk-archive-change

Batch-archive completed OpenSpec changes and resolve delta-spec conflicts.

Official
Advanced