openspec-archive-change

Archive completed experimental changes and sync delta specifications.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill helps manage the lifecycle of experimental changes by archiving completed work, ensuring a clean and organized workflow.

Core Features & Use Cases

  • Automated Archiving: Moves completed change directories to a designated archive location.
  • Status Checks: Verifies artifact and task completion before archiving.
  • Delta Spec Sync: Assesses and optionally syncs delta specifications with main specifications.
  • Use Case: After successfully implementing a new feature defined in an experimental change, use this Skill to archive the change, keeping your active development areas clear.

Quick Start

Use the openspec-archive-change skill to archive the change named 'feature-x'.

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?

You can archive completed experimental changes by moving the change directory to a designated archive location. The process verifies that all artifacts and tasks are accounted for before proceeding with the final archival.

What happens to delta specifications when I archive a change?

When archiving a change, the system assesses delta specifications and optionally synchronizes them with main specifications. This ensures all incremental updates are properly merged before the workflow is finalized.

Can I archive an experimental change if some tasks are incomplete?

Yes, you can archive a change with incomplete items. The workflow supports user confirmation to proceed with the archival, providing a detailed summary of the process to ensure you are aware of unfinished elements.

When should I use a specification sync before archiving?

You should sync specifications when your experimental change includes delta specs that need to be preserved. The archival process assesses these deltas and optionally syncs them with main specifications to maintain project consistency.

Does archiving a change directory clear my active development workspace?

Yes, archiving completed work moves the change directory out of your active development area. This keeps your workspace clean and organized by relocating finished experimental workflows to an archive.