openspec-archive-change

Archive completed workflow changes after verifying artifacts and tasks.

Updated Apr 23, 2026

Search Tags:#workflow management #change archiving #openspec CLI #specification synchronization #change finalization

Ready to run

npx skills add https://github.com/rm-rf-etc/Unbought --skill openspec-archive-change-rm-rf-etc

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/rm-rf-etc/Unbought/tree/main/.opencode/skills/openspec-archive-change
Command: npx skills add https://github.com/rm-rf-etc/Unbought --skill openspec-archive-change-rm-rf-etc

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill simplifies the process of archiving completed changes in an experimental workflow, ensuring that changes are finalized, reviewed, and ready for long-term storage.

Core Features & Use Cases

Finalization of Changes: Securely archive changes that are completed and verified for completion status.
Workflow Verification: Check the status of artifacts and tasks within the change before finalizing.
Spec Synchronization: Optionally synchronize delta specifications with their main counterparts.
Use Case: Perfect for engineering teams who want to mark off changes after successful implementation and keep the workflow organized.

Quick Start

To archive a change, simply use the command: archive_change "change_name". The Skill will automatically verify the status of the change and handle the archiving process.

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 and synchronize delta specifications?▼

Archiving completed changes involves verifying all artifacts and tasks are complete before finalization, with an option to synchronize delta specifications with main specifications. This ensures changes are securely stored and the workflow remains organized.

What is change finalization in a workflow management process?▼

Change finalization is the process of verifying completion status of all artifacts and tasks within a change before securely archiving it for long-term storage. It ensures only reviewed and completed changes are stored in the workflow.

Do I need the openspec CLI to archive changes?▼

Yes, the openspec CLI is required to archive changes. The archiving process depends on the CLI environment and a proper setup for delta specification analysis to verify completion status before finalization.

How do I verify workflow artifacts and tasks before archiving a change?▼

Workflow verification checks the status of artifacts and tasks within a change before finalizing the archiving process. The command `archive_change "change_name"` automatically verifies completion status and handles the archiving.

Can I synchronize delta specifications with main specifications during archiving?▼

Yes, spec synchronization is an optional step during change archiving that merges delta specifications with their main counterparts. This keeps the main specifications updated when completed changes are finalized and archived.

What happens if artifact completion status is not verified before change archiving?▼

Change archiving requires workflow verification to confirm all artifacts and tasks are complete. The process checks completion status before finalization to prevent incomplete changes from being archived in long-term storage.