openspec-archive-change

Archive completed changes after verifying artifacts, tasks, and delta spec sync.

Updated Mar 8, 2026

Search Tags:#workflow #version control #archive #openspec #specification management #experimental changes

Ready to run

npx skills add https://github.com/deicer/codex-lb --skill openspec-archive-change-deicer

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/deicer/codex-lb/tree/main/.agents/skills/openspec-archive-change
Command: npx skills add https://github.com/deicer/codex-lb --skill openspec-archive-change-deicer

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill streamlines the process of archiving completed changes within an experimental workflow, ensuring a clean and organized project history.

Core Features & Use Cases

Automated Archiving: Moves completed changes to a designated archive location.
Status Verification: Checks artifact and task completion before archiving.
Delta Spec Sync: Assesses and optionally syncs delta specifications with main specifications.
Use Case: After implementing a new feature and testing it, use this Skill to formally 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-authentication-flow'.

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 version control?▼

To archive completed experimental changes, you can use a workflow that verifies artifact and task completion status before moving the change to a designated archive directory. This ensures your project history stays clean and organized.

What is the best way to synchronize delta specifications with main specifications?▼

The best way to synchronize delta specifications with main specifications is to assess the delta files first and optionally sync them with the main specifications before moving the change to the archive directory.

When do I need to archive a change in an experimental workflow?▼

You need to archive a change in an experimental workflow after implementing a new feature and testing it. This formally archives the change, ensuring all related artifacts and tasks are accounted for and specifications are up-to-date.

Do I need the openspec CLI to verify artifact and task completion status?▼

Yes, you need the openspec CLI to verify artifact and task completion status. The CLI is required for performing status checks and managing the archival of experimental changes.

Can I archive a specification if artifact and task completion checks are not passing?▼

No, you cannot archive a specification if artifact and task completion checks are not passing. The workflow verifies completion status before allowing the change to move to the archive directory.

Why does synchronizing delta specifications matter before archiving experimental changes?▼

Synchronizing delta specifications matters before archiving experimental changes because it ensures the main specifications are fully up-to-date with the completed work, maintaining accurate project documentation and history.