openspec-archive-change

Archives validated design changes and syncs metadata after confirming with the user.

Updated Mar 9, 2026

Search Tags:#workflow #task management #archive #change management #openspec #specification sync

Ready to run

npx skills add https://github.com/paulotks/CodeLeapTest --skill openspec-archive-change-paulotks

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/paulotks/CodeLeapTest/tree/main/.gemini/skills/openspec-archive-change
Command: npx skills add https://github.com/paulotks/CodeLeapTest --skill openspec-archive-change-paulotks

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 the experimental workflow, ensuring a clean and organized project history.

Core Features & Use Cases

Archive Changes: Moves completed changes to an archive directory, preserving project history.
Status Checks: Verifies artifact and task completion before archiving, providing warnings for incomplete items.
Delta Spec Sync: Assesses and optionally syncs delta specifications with main specifications before archiving.
Use Case: After implementing a new feature and testing it thoroughly, use this Skill to archive the associated 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 '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 changes and sync specifications in a workflow?▼

Archiving completed changes requires verifying all artifacts and tasks are finished, optionally syncing delta specifications with main specifications, and moving the change to an archive directory to preserve project history. The process prompts for confirmation on incomplete items or sync decisions.

What happens if I try to archive changes with incomplete tasks or artifacts?▼

If you attempt to archive changes with incomplete tasks or artifacts, the system performs status checks and provides warnings for incomplete items, prompting you for confirmation before proceeding with the archive operation.

Do I need the openspec CLI to manage change archiving?▼

Yes, the openspec CLI is required to manage change archiving. It is used for performing status checks and managing artifacts during the archive process to ensure specifications are properly synchronized.

How do I synchronize delta specifications with main specifications before archiving?▼

You synchronize delta specifications with main specifications during the archiving process, which assesses the deltas and prompts you to optionally sync them before finalizing the archive, ensuring your main specifications are up-to-date.

Can I specify a change name when archiving completed work?▼

Yes, you can specify a change name when archiving completed work. The archiving process supports optional change name input to target and archive a specific change within your project workflow.