openspec-archive-change

Archive completed OpenSpec changes after validating artifacts and tasks.

Updated May 29, 2025
One-click install
npx skills add https://github.com/carlosapgomes/eqmd --skill openspec-archive-change-carlosapgomes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/carlosapgomes/eqmd/tree/main/.claude/skills/openspec-archive-change
Command: npx skills add https://github.com/carlosapgomes/eqmd --skill openspec-archive-change-carlosapgomes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archive a completed change in the OpenSpec experimental workflow.

Core Features & Use Cases

  • Orchestrates prompting for an active change name if not provided.
  • Checks artifact completion status, verifies task completion, and assesses delta spec synchronization.
  • Archives the change to openspec/changes/archive/YYYY-MM-DD-<name>, preserving relevant metadata and providing a final summary.

Quick Start

Provide a change name to archive, or let the system prompt you to choose an active change.

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 the OpenSpec workflow?

To archive an OpenSpec change, provide the change name or let the system prompt you. It checks artifact and task completion, syncs delta specifications, and relocates the change to the archive directory.

What is delta spec synchronization and when do I need it for archiving?

Delta spec synchronization is an optional step before archiving an OpenSpec change. It assesses whether the delta specifications are properly updated before the change is relocated to the archive directory.

Do I need the OpenSpec CLI to archive completed changes?

Yes, the OpenSpec CLI is required to archive completed changes. The archiving process relies on it to validate artifacts, check task completion, and relocate the change to the archive directory.

Can I archive an OpenSpec change if artifact or task completion is not verified?

No, archiving an OpenSpec change requires checking artifact completion status and verifying task completion. The process validates these conditions before relocating the change to the archive directory.

What happens to OpenSpec change metadata after archiving?

When an OpenSpec change is archived, relevant metadata is preserved during relocation to the openspec/changes/archive/YYYY-MM-DD-<name> directory, and a final summary is provided.