openspec-archive-change

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

Archive completed OpenSpec changes with artifact and delta-spec checks.

7|2|Updated Mar 8, 2026

Search Tags:#workflow #cli #archive #openspec #artifact #change-management #delta-spec

Ready to run

npx skills add https://github.com/sundaiclaw/hacker --skill openspec-archive-change-sundaiclaw

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/sundaiclaw/hacker/tree/main/agent-build-observatory/.claude/skills/openspec-archive-change
Command: npx skills add https://github.com/sundaiclaw/hacker --skill openspec-archive-change-sundaiclaw

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archive a completed change in the OpenSpec experimental workflow.

Core Features & Use Cases

Prompt-driven change selection: If no change name is provided, ask the user to choose from active changes.
Artifact & delta-spec checks: Validate artifact completion and assess delta-spec synchronization before archiving.
Structured archiving: Create a dated archive directory under openspec/changes/archive and move the change, preserving metadata.

Quick Start

Provide the change name to archive and I will finalize and move it to the archive.

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 a completed change in OpenSpec?▼

To archive a completed OpenSpec change, the workflow validates artifact completion and delta-spec alignment, then moves the change directory to openspec/changes/archive with a date prefix while preserving metadata like .openspec.yaml.

Do I need the OpenSpec CLI to archive completed changes?▼

Yes, archiving completed OpenSpec changes requires the OpenSpec CLI to execute the workflow, validate delta-spec synchronization, and move the directory to the dated archive folder.

What happens to .openspec.yaml metadata when I move a change to the archive?▼

When archiving a change, the process preserves metadata like .openspec.yaml by moving it alongside the change directory into openspec/changes/archive with a date prefix.

Can I select which change to archive if I don't specify a name?▼

Yes, if no change name is provided, the prompt-driven workflow asks the user to select an active change from the available list before validating and archiving it.

When should I archive an OpenSpec change?▼

You should archive an OpenSpec change when the work is finalized, artifacts are complete, and delta-spec alignment is verified, making the change ready for structured documentation and storage.

What's the best way to verify delta-spec alignment before archiving a change?▼

The best way to verify delta-spec alignment is to use the OpenSpec archiving workflow, which automatically checks artifact completion and delta-spec synchronization before moving the change to the archive.