openspec-archive-change

Archive completed OpenSpec changes after validating artifacts and tasks.

Updated May 29, 2025

Search Tags:#automation #workflow #devops #archive #openspec #change-management #spec-sync

Ready to run

npx skills add https://github.com/crozzbite/DnDApp --skill openspec-archive-change-crozzbite

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archives completed OpenSpec changes in the experimental workflow to finalize work and keep history organized.

Core Features & Use Cases

Validates artifact and task completion, ensuring all required artifacts are done before archiving.
Checks for delta specs and assists in syncing with main specs when present.
Archives the change into a dated archive folder under openspec/changes/archive and reports a clear summary.

Quick Start

Provide the change name to archive, or let the system prompt you to choose, then initiate the archive flow.

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 safely?▼

To archive OpenSpec changes safely, the system validates all artifacts and tasks, syncs delta specs, and moves the finalized change into a dated folder under openspec/changes/archive.

What is the process for syncing delta specs before finalizing an OpenSpec change?▼

Syncing delta specs during OpenSpec change finalization involves detecting pending delta specs and assisting in merging them with main specs before the change is moved to the archive folder.

How does OpenSpec check if a change is ready for archiving?▼

OpenSpec checks archiving readiness by running openspec status --json to validate that all required artifacts and tasks associated with the experimental workflow change are fully completed.

Do I need to manually specify the change name to start the OpenSpec archive workflow?▼

You do not need to manually specify the change name; you can provide it directly to initiate the archive flow, or let the system prompt you to choose from available completed changes.

What happens to the .openspec.yaml file when a change is archived?▼

When a change is archived, the workflow explicitly preserves the .openspec.yaml configuration file, ensuring the change context is maintained intact within the openspec/changes/archive directory.

Why does my OpenSpec change fail to archive even when tasks are done?▼

OpenSpec change archiving may fail if openspec status --json reports incomplete artifacts, or if unresolved delta specs exist that have not been properly synced with the main specifications.