openspec-archive-change

Archive a completed OpenSpec change with validated artifacts and metadata.

241|31|Updated Mar 28, 2026

Search Tags:#workflow #archive #openspec #change-management #artifact-tracking #spec-sync

Ready to run

npx skills add https://github.com/rayxuln/hastur-operation-plugin --skill openspec-archive-change-rayxuln

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/rayxuln/hastur-operation-plugin/tree/main/.opencode/skills/openspec-archive-change
Command: npx skills add https://github.com/rayxuln/hastur-operation-plugin --skill openspec-archive-change-rayxuln

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archive a completed change in the experimental workflow. Use when finalizing and archiving a change after implementation is complete.

Core Features & Use Cases

Validate artifact completion status via openspec status to ensure all artifacts are finished before archiving.
Validate task completion status by inspecting tasks.md for any incomplete tasks, prompting user as needed.
Assess delta specs sync state and optionally synchronize with main specs before archiving.
Create a dated archive path under openspec/changes/archive and move the change directory, preserving metadata including .openspec.yaml.
Provide a clear summary of actions taken and any warnings encountered during the archive process.

Quick Start

Provide the change name to archive, then run the archive flow to confirm artifacts, tasks, and delta specs before finalizing.

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 OpenSpec changes after implementation?▼

To archive completed OpenSpec changes, the workflow validates artifact readiness, checks task completion, and optionally syncs delta specs before moving the change directory to a dated archive path, preserving original metadata like .openspec.yaml.

Can I synchronize delta specs with main specs before archiving an OpenSpec change?▼

You can assess delta spec sync states and optionally synchronize them with main specs before archiving, ensuring the primary specifications are updated prior to moving the completed change to the archive path.

What happens to OpenSpec metadata when moving a change to the archive directory?▼

When archiving an OpenSpec change, the process creates a dated path under openspec/changes/archive and moves the directory while preserving original metadata, including the .openspec.yaml configuration file.

Why does my OpenSpec change archive process prompt me about incomplete tasks?▼

The OpenSpec change archive process prompts you about incomplete tasks because it inspects tasks.md to validate task completion status, ensuring no unfinished work remains before finalizing the archive.

When should I avoid archiving an OpenSpec change?▼

You should avoid archiving an OpenSpec change if openspec status indicates unfinished artifacts or if tasks.md contains incomplete tasks, as the archive process requires verified implementation and task completion.