openspec-archive-change

Archive completed openspec experimental changes after verifying artifacts and tasks.

10|Updated Jan 28, 2026

Search Tags:#workflow #task management #archive #openspec #spec synchronization #experimental changes

Ready to run

npx skills add https://github.com/AGIBuild/Agibuild.Fulora --skill openspec-archive-change-agibuild

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/AGIBuild/Agibuild.Fulora/tree/main/.cursor/skills/openspec-archive-change
Command: npx skills add https://github.com/AGIBuild/Agibuild.Fulora --skill openspec-archive-change-agibuild

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill helps manage the experimental workflow by archiving completed changes, ensuring a clean and organized project structure.

Core Features & Use Cases

Automated Archiving: Moves completed changes to a designated archive location.
Status Checks: Verifies artifact and task completion before archiving.
Spec Synchronization: Assesses and optionally syncs delta specs with main specs.
Use Case: After successfully implementing and testing a new feature, use this Skill to archive the associated experimental change, marking it as complete and organized.

Quick Start

Use the openspec-archive-change skill to archive the change named 'new-user-authentication'.

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 experimental changes in an openspec workflow?▼

To archive completed experimental changes, this skill moves finalized changes to a historical archive location, requiring the openspec CLI to verify artifact and task completion before organizing the project structure.

What is the best way to synchronize delta specifications after archiving an experimental change?▼

Synchronizing delta specifications is handled optionally during the archiving process, assessing and syncing delta specs with main specs using the openspec CLI to ensure project artifacts remain consistent.

Do I need the openspec CLI to verify task completion before archiving experimental changes?▼

Yes, the openspec CLI is required to perform status checks, verifying that all artifacts and tasks associated with the experimental change are complete before moving them to the archive.

When should I archive an experimental change in my task management workflow?▼

You should archive an experimental change after successfully implementing and testing a new feature, using this process to mark the development as complete and maintain an organized project structure.

Can I use openspec to automatically move finalized experimental changes to a historical archive?▼

Yes, automated archiving moves completed changes to a designated historical archive location, verifying artifact and task completion through the openspec CLI to ensure only finalized changes are moved.

Why does archiving experimental changes require verifying artifact and task completion?▼

Verifying artifact and task completion is required during archiving to ensure only fully finalized and tested experimental changes are moved to the historical archive, preventing incomplete work from disorganizing the project structure.