openspec-archive-change

Archive completed changes with artifact checks and optional delta-spec sync.

Updated Nov 17, 2025
One-click install
npx skills add https://github.com/Valynt/ValueOS --skill openspec-archive-change-valynt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/Valynt/ValueOS/tree/main/.windsurf/skills/openspec-archive-change
Command: npx skills add https://github.com/Valynt/ValueOS --skill openspec-archive-change-valynt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archive completed changes from the experimental workflow to keep history clean and auditable.

Core Features & Use Cases

  • Automated checks of artifact and task completion prior to archiving.
  • Optional delta-spec synchronization to align with main specs.
  • Safe archival with timestamped packaging and preserved provenance.

Quick Start

Use the openspec-archive-change tool to select a completed change and initiate the archive 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 workflow changes to keep project history auditable?

You can archive completed changes by selecting the target change interactively, verifying artifact and task completion, and packaging it into a timestamped directory under openspec/changes/archive to ensure traceability and history integrity.

What is delta-spec synchronization and when do I need it during change archival?

Delta-spec synchronization aligns experimental change specifications with main specs during the archive process. You need it when finalizing a change to ensure main specs reflect completed work without manually merging differences.

Can I archive a change if artifact and task statuses are not fully complete?

Archiving requires all artifact and task completion checks to pass first. The tool enforces these automated checks prior to archival to ensure only fully finalized changes are safely packaged and moved to the archive directory.

What is the best way to safely archive OpenSpec changes without losing provenance?

The best way to archive OpenSpec changes safely is using automated archival with timestamped packaging. This approach preserves provenance by moving completed artifacts to openspec/changes/archive while maintaining full traceability of original workflow history.

Does the change archival process provide a summary of the archived artifacts?

Yes, the change archival process generates a final operation summary after archiving. This summary details the selected change, artifact status checks, delta-spec synchronization results, and the timestamped packaged directory.