openspec-archive-change

Archive completed experimental changes after verifying artifacts and tasks.

1|Updated Feb 11, 2026

Search Tags:#workflow #archive #change management #openspec #specification sync #experimental development

Ready to run

npx skills add https://github.com/vidos-id/usecase-demos --skill openspec-archive-change-vidos-id

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/vidos-id/usecase-demos/tree/main/.agents/skills/openspec-archive-change
Command: npx skills add https://github.com/vidos-id/usecase-demos --skill openspec-archive-change-vidos-id

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (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

Archive completed changes: Moves a completed change to an archive directory.
Status Checks: Verifies artifact and task completion before archiving.
Spec Sync Assessment: Assesses and optionally syncs delta specifications with main specifications.
Use Case: After implementing a new feature defined in an experimental change, use this Skill to archive the change, ensuring all related artifacts and tasks are accounted for and specifications are up-to-date.

Quick Start

Use the openspec-archive-change skill to archive the change named 'user-profile-update'.

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 development workflow?▼

To archive completed changes, the workflow verifies all artifacts and tasks are complete, assesses specification synchronization, and moves the change directory to an archive location while providing a summary of the operation and any warnings encountered.

What is specification sync and when do I need it during change archiving?▼

Specification sync is the process of aligning delta specifications with main specifications. You need it when archiving completed experimental changes to ensure all modified specifications are up-to-date before the work is permanently moved to the archive.

Can I move a change directory to an archive if tasks are not yet verified?▼

No, you cannot archive a change directory if tasks are not verified. The archiving mechanism performs status checks to ensure artifact and task completion is fully verified before allowing the directory to be moved.

Does the change archiving process warn me about missing artifacts or sync issues?▼

Yes, the change archiving process provides a summary of the operation and explicitly warns you about any missing artifacts, unverified tasks, or specification synchronization issues encountered during the directory move.

What is the best way to manage experimental development lifecycle cleanup?▼

The best way to manage experimental development lifecycle cleanup is to archive completed work by moving change directories to a dedicated location, which ensures a clean workflow and verifies all artifacts and specifications are synchronized.

Are there limitations when archiving changes with incomplete specification synchronization?▼

Yes, a key limitation is that archiving changes with incomplete specification synchronization can result in warnings, as the process assesses and optionally syncs delta specifications with main specifications to prevent outdated archives.