openspec-archive-change

Archive completed OpenSpec changes after validating artifact status and delta specs.

68|7|Updated Apr 6, 2026
One-click install
npx skills add https://github.com/drakulavich/kesha-voice-kit --skill openspec-archive-change-drakulavich
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/drakulavich/kesha-voice-kit/tree/main/.claude/skills/openspec-archive-change
Command: npx skills add https://github.com/drakulavich/kesha-voice-kit --skill openspec-archive-change-drakulavich

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archive completed OpenSpec changes by guiding the user through selection, validation, delta-spec syncing, and safe archiving to a centralized archive, preserving history and ensuring compliance with workflow constraints.

Core Features & Use Cases

  • Prompt-driven change selection when none is provided, ensuring the right change is archived.
  • Artifact status checks via openspec status to confirm all artifacts are done before archiving.
  • Delta-spec synchronization assessment with a combined summary before prompting to archive.
  • Safe archive operation that preserves tooling metadata and the .openspec.yaml file.
  • Clear post-archive summary reporting of outcome and any warnings.
  • Use Case: You finished implementing a change and want to move it to the official archive to track completion.

Quick Start

Provide the change name to archive and follow the on-screen prompts to complete the archival.

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 OpenSpec change safely?

To safely archive completed OpenSpec changes, the workflow verifies artifact status via openspec status, syncs delta specs, and moves the finalized work-in-progress to an auditable centralized archive while preserving tooling metadata.

What happens if my artifacts are not complete before archiving an OpenSpec change?

Archiving an OpenSpec change requires artifact status checks to confirm all artifacts are done. If validation fails, the workflow halts to ensure task resolution and artifact completeness before allowing the safe archive operation.

How does delta-spec synchronization work during the change archiving process?

Delta-spec synchronization assesses pending changes and generates a combined summary before prompting you to archive. This ensures your delta specs are synced and reviewed prior to the final OpenSpec archival operation.

Can I archive OpenSpec changes without specifying the change name?

Yes, the workflow features prompt-driven change selection. If no specific change name is provided, it guides you through selecting the correct OpenSpec change to ensure the proper work-in-progress item is archived.

Does archiving an OpenSpec change preserve tooling metadata and configuration files?

Yes, the safe archive operation preserves tooling metadata and the .openspec.yaml file. It generates a structured archive with a summary, ensuring compliance with workflow constraints and maintaining your configuration history.