openspec-archive-change

Archive completed changes in the experimental workflow with openspec CLI.

1|Updated Nov 7, 2025
One-click install
npx skills add https://github.com/harqian/wifi-client --skill openspec-archive-change-harqian
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/harqian/wifi-client/tree/main/.gemini/skills/openspec-archive-change
Command: npx skills add https://github.com/harqian/wifi-client --skill openspec-archive-change-harqian

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill streamlines the process of finalizing and archiving changes in the experimental workflow, providing a structured way to organize completed changes.

Core Features & Use Cases

  • Change Selection: Allows users to select a specific change for archiving.
  • Artifact Completion Status: Verifies that all artifacts are complete before archiving.
  • Task Completion Status: Checks the status of tasks related to the change.
  • Delta Spec Sync State: Handles the synchronization of delta specs with main specs if necessary.
  • Archive Operation: Performs the actual archiving process with a summary of actions taken.

Quick Start

To archive a completed change, use the 'openspec-archive-change' skill and specify the change name or let the system infer it from context.

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 experimental workflow?

To archive completed changes in an experimental workflow, you can use a structured archiving process that verifies artifact and task completion. This ensures all necessary checks pass and delta spec synchronization is managed before finalizing the change.

What checks are required before archiving a change in configuration management?

Before archiving a change in configuration management, the system verifies artifact completion status, checks related task completion status, and handles delta spec synchronization. These checks ensure all components are finalized before the actual archiving process begins.

How do delta specs synchronize with main specs during change archiving?

Delta spec synchronization handles merging delta specs with main specs if necessary during the archiving process. This ensures the main specifications reflect the completed changes before the change is finalized and moved to the archive.

Do I need the openspec CLI to finalize and archive completed changes?

Yes, you need the openspec CLI and associated tools to automate the archiving of completed changes. The system requires these dependencies to perform necessary checks, manage delta spec synchronization, and execute the archive operation.

Can I select a specific change for archiving automatically?

Yes, you can specify a change name to select a specific change for archiving, or let the system infer the change from context. This allows flexibility when finalizing individual changes within the experimental workflow.

What happens if artifact or task completion checks fail before archiving?

The archiving process verifies all artifacts and tasks are complete before proceeding. If these completion checks fail, the system prevents the archive operation to ensure only fully finalized changes are archived in the workflow.