openspec-archive-change

Archives a completed change into openspec/changes/archive with a date-based name.

17|1|Updated Mar 14, 2025

Search Tags:#automation #workflow #artifacts #archive #openspec #changes #specs

Ready to run

npx skills add https://github.com/deckgl-fiber-renderer/fiber.gl --skill openspec-archive-change-deckgl-fiber-renderer

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/deckgl-fiber-renderer/fiber.gl/tree/main/.claude/skills/openspec-archive-change
Command: npx skills add https://github.com/deckgl-fiber-renderer/fiber.gl --skill openspec-archive-change-deckgl-fiber-renderer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archive a completed change in the experimental workflow.

Core Features & Use Cases

Coordinates change selection when a change name is provided or prompts for available changes
Validates artifact completion status via openspec status and ensures all artifacts are done
Checks task completion against tasks.md and surfaces incomplete tasks before archiving
Assesses delta-spec synchronization against main specs and suggests syncing if delta exists
Archives the change under openspec/changes/archive/YYYY-MM-DD-<name> with a date-based name
Preserves critical metadata (e.g., .openspec.yaml) during the move and reports a clear summary
Provides a structured summary after archiving, including whether specs were synced and any warnings

Quick Start

Supply the change name to archive, and let the tool validate artifacts, tasks, and delta specs before moving the change into openspec/changes/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 completed openspec changes in my workflow?▼

To archive completed openspec changes, you supply the change name and the tool validates artifact statuses, task completion, and delta-spec synchronization before moving it to openspec/changes/archive with a date-based naming scheme.

What happens if openspec tasks are not completed before archiving?▼

If openspec tasks are not completed, the tool checks completion against tasks.md and surfaces incomplete tasks before archiving, prompting for missing inputs and enforcing guardrails to prevent premature archival.

Does archiving an openspec change preserve existing .openspec.yaml metadata?▼

Yes, archiving an openspec change preserves critical metadata like .openspec.yaml during the move to the archive directory, ensuring configuration remains intact throughout the archival process.

How does delta-spec synchronization work when archiving openspec changes?▼

Delta-spec synchronization assesses delta specs against main specs during archiving and suggests syncing if delta exists, ensuring spec changes are reconciled before the change is archived.

Can I select which openspec change to archive when multiple changes exist?▼

Yes, you can provide a specific change name to archive, or the tool will prompt you with available changes to select from, coordinating change selection automatically when needed.

Why does openspec archive validation fail for incomplete artifacts?▼

Openspec archive validation fails for incomplete artifacts because the tool validates completion status via openspec status and enforces that all artifacts are done before allowing archival to proceed.