openspec-archive-change

Archive completed workflow changes with openspec CLI verification.

Updated Jan 4, 2026
One-click install
npx skills add https://github.com/rahmatullahboss/multi-store-saas --skill openspec-archive-change-rahmatullahboss
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/rahmatullahboss/multi-store-saas/tree/main/.qwen/skills/openspec-archive-change
Command: npx skills add https://github.com/rahmatullahboss/multi-store-saas --skill openspec-archive-change-rahmatullahboss

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill facilitates the systematic archiving of completed changes within the experimental workflow, ensuring version control and traceability.

Core Features & Use Cases

  • Change Selection: Allows users to identify and select active changes for archiving, with prompts if no change name is provided.
  • Artifact and Task Verification: Checks if all related artifacts and tasks are completed or pending, alerting about incompletions.
  • Delta Specification Management: Compares delta specs with main specs, providing detailed summaries and options to synchronize before archiving.
  • Archiving Process: Moves finalized change directories into an organized archive structure, preventing overwrites and maintaining historical records.

Quick Start

Instruct the AI to identify an active change, verify all work is complete, optionally synchronize specifications, and then archive the change into a timestamped directory.

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 workflow changes in version control?

Archiving completed workflow changes involves verifying artifact completeness, comparing delta specifications, and moving finalized directories into a structured archive to maintain version control and traceability.

What is change finalization in specification management?

Change finalization in specification management is the process of verifying completed tasks, synchronizing delta specs with main specs, and securely archiving the change records for historical traceability.

How do I verify artifact completeness before archiving a change?

Verifying artifact completeness requires checking if all related tasks are completed or pending, alerting about any incompletions, and running status checks before moving the change directory into the archive.

Can I synchronize delta specifications with main specs during archiving?

Yes, you can synchronize delta specifications with main specs during archiving by comparing the two, reviewing detailed summaries of differences, and applying updates before finalizing the workflow change.

Does the openspec CLI support preventing overwrites in the archive structure?

Yes, the archiving process uses the openspec CLI to move finalized change directories into timestamped folders, preventing overwrites and maintaining organized historical records without data loss.

What happens if I archive a change with pending tasks?

If you archive a change with pending tasks, the artifact and task verification step will alert you about the incompletions, allowing you to address the pending work before finalizing the archive.