openspec-archive-change

Archive completed openspec changes after validating artifacts and tasks.

4|2|Updated Aug 27, 2025
One-click install
npx skills add https://github.com/finger-gun/sisu --skill openspec-archive-change-finger-gun
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/finger-gun/sisu/tree/main/.kilocode/skills/openspec-archive-change
Command: npx skills add https://github.com/finger-gun/sisu --skill openspec-archive-change-finger-gun

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archive completed changes in the experimental workflow to ensure proper provenance, archive organization, and reproducibility while preserving related specs and artifacts.

Core Features & Use Cases

  • Guided archival workflow: select a change, validate artifact and task completion, and archive to a dated archive directory.
  • Delta-spec handling: assess and optionally sync delta specs with main specs before archiving.
  • Safe-guard rails: prompt for change selection if not provided and report a clear archival summary.

Quick Start

Provide the change name when prompted to begin the archival workflow and follow the guided prompts to validate, optionally synchronize specs, and move the change to archive.

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 while preserving artifacts?

To archive completed openspec changes, this workflow validates artifact and task completion, optionally syncs delta specs, and moves the change to a dated archive directory while preserving the original openspec.yaml and related artifacts.

What happens to delta specs when archiving an openspec change?

Delta specs are assessed during the openspec change archival process, and you can optionally synchronize them with main specs before the change is moved to the archive directory.

How do I validate tasks and artifacts before moving a change to the archive?

Validating tasks and artifacts before archival involves a guided workflow that checks completion status, reports warnings or skipped steps, and ensures the original openspec.yaml is preserved during the move.

Can I archive a specific change without being prompted for a name?

Yes, you can provide the change name upfront to begin the archival workflow directly; if a change name is not provided, the system will prompt you to select from only active changes.

Does the openspec archive workflow report the final archive location?

Yes, the workflow reports a final status that includes the archive location and whether specs were synced, providing a clear summary of the archival process and any warnings.

What safeguards exist when moving completed changes to an openspec archive?

Safeguards include prompting for change selection if not provided, showing only active changes, validating completion, and preserving the original openspec.yaml and related artifacts during the move to prevent data loss.