openspec-archive-change

Name: openspec-archive-change
Availability: InStock
Author: Halo

Validate artifact status and task completion before archiving experimental changes.

6|4|Updated May 11, 2026

Search Tags:#workflow #archive #change management #openspec #spec sync

Ready to run

npx skills add https://github.com/halo-dev/plugin-ai-foundation --skill openspec-archive-change-halo-dev

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/halo-dev/plugin-ai-foundation/tree/main/.claude/skills/openspec-archive-change
Command: npx skills add https://github.com/halo-dev/plugin-ai-foundation --skill openspec-archive-change-halo-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you finalize an experimental change by validating its completion state, warning about unfinished work, and archiving it into the proper history location without losing context.

Core Features & Use Cases

Change Selection: Lists available active changes and prompts the user to choose when no name is provided.
Completion Checks: Verifies artifact status and task completion before archiving, surfacing incomplete items for confirmation.
Delta Spec Handling: Detects spec drift, summarizes needed sync actions, and supports syncing before archive when appropriate.
Safe Archival: Moves the change into a dated archive path and prevents overwrite conflicts.
Use Case: A developer finishes implementing a workflow change and uses this Skill to confirm everything is ready, optionally sync specs, and archive the change cleanly.

Quick Start

Use this skill to archive the completed change named "my-change" after checking its artifacts and tasks.

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 open specification changes safely?▼

To archive completed open specification changes safely, this Skill validates artifact status, checks task completion, detects spec drift, and moves the change into a dated archive path to prevent data loss and overwrite conflicts.

What happens if I try to archive an openspec change with incomplete tasks?▼

When archiving an openspec change with incomplete tasks, the Skill surfaces unfinished work and incomplete artifact statuses, prompting you for confirmation before proceeding with the archival process.

Can I synchronize spec deltas before moving a workflow change to the archive?▼

Yes, you can synchronize spec deltas before moving a workflow change to the archive. The Skill detects spec drift, summarizes needed sync actions, and supports syncing specs during the archival process.

Do I need the openspec CLI to finalize and archive experimental changes?▼

Yes, you need the openspec CLI to finalize and archive experimental changes, as the Skill requires CLI access to validate completion states and move data into the proper history location.

How do I select a specific change when archiving workflow changes without a name?▼

When archiving workflow changes without a name, the Skill lists available active changes and prompts you to select the correct one, resolving ambiguity before running completion checks and archiving.