openspec-archive-change

Archive completed changes after verifying artifacts and syncing delta specifications.

5|1|Updated Jan 31, 2026

Search Tags:#workflow #development #version control #archive #change management #openspec

Ready to run

npx skills add https://github.com/yuboon/ai-examples --skill openspec-archive-change-yuboon

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/yuboon/ai-examples/tree/main/002-springboot-mcp/.claude/skills/openspec-archive-change
Command: npx skills add https://github.com/yuboon/ai-examples --skill openspec-archive-change-yuboon

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill helps you finalize and archive completed changes within an experimental workflow, ensuring a clean and organized project history.

Core Features & Use Cases

Automated Archiving: Moves completed changes to an archive directory with a timestamped name.
Status Checks: Verifies artifact and task completion before archiving.
Delta Spec Sync: Assesses and optionally syncs delta specifications before archiving.
Use Case: After implementing a new feature and testing it, you can use this Skill to archive the development work, marking it as complete and organized.

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

To archive completed changes in an openspec workflow, you use a change management process that verifies artifact and task completion before moving the change directory to a timestamped archive location.

What is the best way to sync delta specifications before archiving a change?▼

Syncing delta specifications before archiving involves assessing and optionally merging delta specs against main specifications to ensure your version control history is clean and organized.

Do I need the openspec CLI to archive a completed change?▼

Yes, you need the openspec CLI to archive a completed change, as the CLI is required to perform status checks and list changes before the archiving process moves your files.

What happens if my artifact and task completion checks fail during change archiving?▼

If artifact and task completion checks fail during change archiving, the process prevents moving the change directory to the archive, ensuring only fully verified development work is finalized.

Can I automate moving completed development work to a timestamped archive directory?▼

Yes, you can automate moving completed development work to a timestamped archive directory using change management scripts that verify delta spec synchronization and task completion beforehand.

When should I archive a change in my development workflow?▼

You should archive a change in your development workflow after implementing a new feature, testing it, and verifying that all associated artifacts and tasks are fully complete.