openspec-archive-change

Archive completed changes after verifying artifacts, tasks, and delta specs.

Updated Apr 3, 2026
One-click install
npx skills add https://github.com/pertrai1/open-forge --skill openspec-archive-change-pertrai1
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/pertrai1/open-forge/tree/main/.cursor/skills/openspec-archive-change
Command: npx skills add https://github.com/pertrai1/open-forge --skill openspec-archive-change-pertrai1

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill manages the archiving process for completed changes within an experimental workflow, providing a streamlined way to finalize and securely store changes after they have been implemented.

Core Features & Use Cases

  • Change Archiving: Automates the finalization and archiving of changes in an experimental workflow.
  • User Selection: Offers a user-friendly interface for selecting changes to archive.
  • Status Checking: Ensures that artifacts and tasks are completed before archiving.
  • Delta Spec Syncing: Optionally syncs delta specs with main specs before archiving.

Quick Start

Archive a completed change using 'archive-change --change <change-name>'.

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, use the 'archive-change --change <change-name>' command. This initiates the archiving process by verifying that all artifacts and tasks are completed, and optionally syncing delta specs with main specs before finalizing the storage.

What checks are performed before archiving a change?

Before archiving a change, the system performs checks for artifact completion, task completion, and delta spec sync status. These checks ensure that only fully implemented and finalized changes are securely stored in the archive.

Do I need openspec CLI to archive changes?

Yes, the openspec CLI is a required dependency for archiving changes. The Skill relies on the CLI to execute the series of pre-archiving checks and to manage the finalization of changes within the experimental workflow.

Can I sync delta specs with main specs during the archiving process?

Yes, delta spec syncing is an optional step during the archiving process. You can sync delta specs with main specs before archiving to ensure your specification documents are fully up to date before the change is finalized and stored.

Why does change archiving fail in my workflow automation?

Change archiving fails when pre-archiving checks detect incomplete artifacts or unfinished tasks. The system requires all tasks and artifacts associated with the change to be fully completed before allowing the archiving process to proceed.

What is the best way to manage completed change archiving in version control?

The best way to manage completed change archiving is to automate the finalization process using a dedicated workflow tool. This ensures artifact and task completion checks are systematically verified before securely storing the finalized changes.