skills.rest
roger8b
roger8bCOMMUNITY
Explore all skills by this author →
GitHub

openspec-archive-change

Archive completed experimental workflow changes using the openspec CLI.

Updated Mar 8, 2026
Search Tags:#workflow automation#archiving#change management#spec sync#archive change
One-click install
npx skills add https://github.com/roger8b/slideflow --skill openspec-archive-change-roger8b
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/roger8b/slideflow/tree/main/.gemini/skills/openspec-archive-change
Command: npx skills add https://github.com/roger8b/slideflow --skill openspec-archive-change-roger8b

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires openspec, openspec-sync-specs, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the process of archiving completed changes in the experimental workflow, ensuring that changes are finalized and stored securely after implementation.

Core Features & Use Cases

  • Archive Changes: Archive completed changes in the experimental workflow.
  • Change Selection: Prompt for change selection if no name is provided.
  • Artifact Completion Check: Verify completion status of artifacts before archiving.
  • Task Completion Check: Verify completion status of tasks before archiving.
  • Spec Sync Assessment: Assess and sync delta specs with main specs if applicable.
  • Archive Execution: Move the change directory to the archive location.
  • Summary Display: Provide a summary of the archiving process.

Quick Start

Run the 'archive-change' command to finalize and archive a completed 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 the experimental workflow?▼

To archive completed changes in the experimental workflow, run the archive-change command via the openspec CLI. The process verifies artifact and task completion status, assesses spec sync, and prompts for confirmation before moving the change directory to the archive location.

What happens if my artifacts or tasks are not completed before archiving?▼

Before archiving, the workflow checks the completion status of artifacts and tasks. If artifacts or tasks are incomplete, the process identifies the missing elements and prompts for user confirmation to prevent prematurely finalizing and archiving incomplete changes.

Does the archiving process sync delta specs with main specs?▼

Yes, the archiving process includes a spec sync assessment that evaluates delta specs and synchronizes them with main specs if applicable. This ensures main specifications remain current before the change directory is moved to the archive.

Do I need openspec-sync-specs to finalize and archive a change?▼

Yes, you need both the openspec and openspec-sync-specs skills installed. The archiving process relies on openspec CLI for execution and requires openspec-sync-specs to properly assess and synchronize delta specs with main specs before finalizing.

Can I archive a change without providing a specific change name?▼

Yes, you can archive a change without a specific name. If no change name is provided, the system will automatically prompt for change selection, allowing you to choose the correct completed change from the available list before proceeding.

Related Skills

Explore More Software Engineering Skills→
ywh0606ywh0606

opsx-verify

Verify OpenSpec changes for completion and readiness before archiving.

Community
Intermediate
tenondecrpctenondecrpc
3

openspec-archive-change

Automate archiving completed changes in an experimental workflow.

Community
Advanced
jankneumannjankneumann
4

openspec-archive-change

Archive completed OpenSpec change directories to a dated location.

Community
Advanced
jason23452jason23452

openspec-archive-change

Archive completed changes while preserving .openspec.yaml configuration.

Community
Advanced