openspec-archive-change

Archive completed openspec changes into date-based directories with validation.

2|Updated Sep 23, 2025
One-click install
npx skills add https://github.com/tonysyu/gqlxp --skill openspec-archive-change-tonysyu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/tonysyu/gqlxp/tree/main/.claude/skills/openspec-archive-change
Command: npx skills add https://github.com/tonysyu/gqlxp --skill openspec-archive-change-tonysyu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archive completed changes in experimental workflows to finalize and preserve state.

Core Features & Use Cases

  • Validate artifact and task completion before archiving.
  • Assess delta spec synchronization and preserve provenance during archiving.
  • Archive changes to openspec/changes/archive/YYYY-MM-DD-<name> with date-based naming and optional prompts.

Quick Start

Archive a completed change using the openspec CLI to initiate the archival process.

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 changes in an openspec workflow?

To archive completed changes in openspec, the Skill validates artifact and task completion, assesses delta spec synchronization, and moves the change directory into a date-based archive while preserving provenance.

What is the best way to preserve provenance when archiving spec changes?

Preserving provenance during spec change archiving is handled automatically by validating task completion and delta spec synchronization before moving the change directory into the openspec archive.

Do I need the openspec CLI to archive change directories?

Yes, you need the openspec CLI and appropriate permissions to access and modify the relevant openspec/changes directories to initiate the archival process.

Can I validate artifact and task completion before moving changes to the archive?

Yes, validating artifact and task completion is a mandatory guardrail that runs before archiving to ensure the change directory is fully finalized and synchronized.

Why does the archive process use date-based naming for change directories?

Date-based naming organizes archived changes into openspec/changes/archive/YYYY-MM-DD-<name> directories, ensuring chronological tracking and easy retrieval of finalized change artifacts.

What happens if delta spec synchronization fails during openspec archiving?

If delta spec synchronization is incomplete, the archival process includes guardrails and optional prompts to prevent moving unfinished changes into the date-based archive.