openspec-archive-change

Validate and archive completed OpenSpec changes with optional delta spec sync.

Updated Apr 13, 2026
One-click install
npx skills add https://github.com/soyrochus/vulgata --skill openspec-archive-change-soyrochus
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/soyrochus/vulgata/tree/main/.claude/skills/openspec-archive-change
Command: npx skills add https://github.com/soyrochus/vulgata --skill openspec-archive-change-soyrochus

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines the finalization and archival of an OpenSpec change by validating completion, prompting the user for decisions, optionally syncing delta specs, and moving the change into a dated archive folder so repository state remains organized and auditable.

Core Features & Use Cases

  • Guided Selection: Prompts the user to select an active change when the name is not provided, avoiding accidental archives.
  • Completion Checks: Uses openspec CLI status and tasks files to detect incomplete artifacts or tasks and requests confirmation before proceeding.
  • Delta Spec Assessment & Sync: Analyzes delta specs versus main specs, summarizes diffs, and offers to sync before archiving.
  • Safe Archival Operation: Creates a dated archive folder, verifies target non-existence, preserves .openspec.yaml, and moves the change directory.
  • Use Case: Maintainers finalizing a completed feature or spec change and wanting a reproducible, auditable archive with optional spec synchronization.

Quick Start

Ask the assistant to archive the OpenSpec change named payment-api, confirm any warnings about incomplete artifacts or tasks, and sync delta specs if desired.

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 an OpenSpec change after completion?

To archive an OpenSpec change, validate artifacts and tasks using openspec CLI status, optionally sync delta specs to main specs, then move the change directory into a dated archive folder. The process requires explicit user confirmation if incomplete items are detected.

What happens to delta specs when I archive an OpenSpec change?

Delta specs are analyzed against main specs to summarize diffs before archival. The Skill offers to sync delta specs to main specs, preserving spec consistency before moving the change directory into the archive.

Does the OpenSpec archival process require the openspec CLI?

Yes, archiving an OpenSpec change requires the openspec CLI for list and status commands. It also requires repository filesystem write access under openspec/changes to move directories and preserve .openspec.yaml.

Can I archive an OpenSpec change with incomplete artifacts or tasks?

You can archive an OpenSpec change with incomplete artifacts or tasks, but the Skill detects them using openspec CLI status and tasks files, then requires explicit user confirmation before proceeding with the archival operation.

Why is my OpenSpec change not being archived safely?

Safe archival requires verifying target non-existence, preserving .openspec.yaml, and creating a dated archive folder. If repository filesystem write access under openspec/changes is missing, the operation cannot move the change directory.

What is the best way to finalize a completed OpenSpec feature?

The best way to finalize a completed OpenSpec feature is guided selection of the active change, completion checks via openspec CLI, optional delta spec sync, and moving the directory into a dated archive folder for an auditable repository state.