openspec-archive-change

Archive completed OpenSpec change directories with validation and timestamped relocation.

Updated Nov 29, 2022

Search Tags:#workflow #validation #archiving #change management #openspec #specs

Ready to run

npx skills add https://github.com/circlebacknever/soundstage --skill openspec-archive-change-circlebacknever

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/circlebacknever/soundstage/tree/main/.codex/skills/openspec-archive-change
Command: npx skills add https://github.com/circlebacknever/soundstage --skill openspec-archive-change-circlebacknever

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the manual friction of finishing an OpenSpec change by guiding you through selection, validation, optional syncing, and safe archival in one controlled workflow.

Core Features & Use Cases

Change Finalization: Select the correct active change when the name is missing or ambiguous.
Completion Checks: Review artifact status and task completion before archiving so unfinished work is surfaced early.
Delta Spec Handling: Compare delta specs against main specs and optionally sync them before the archive move.
Safe Archival: Move the completed change into a dated archive path without overwriting an existing archive.
Use Case: A development team finishes a feature change, confirms all tasks are done, syncs any spec updates, and archives the work for historical tracking.

Quick Start

Use this skill to archive the completed OpenSpec change named feature-x after confirming it is ready to close.

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 safely without losing data?▼

Archiving completed OpenSpec changes safely requires validating task completion, reviewing delta specs, and relocating the change directory into a timestamped archive path to prevent overwriting existing historical records.

What is the best way to finalize and archive an OpenSpec change directory?▼

Finalizing an OpenSpec change directory involves selecting the active change, checking artifact completion status, optionally syncing delta specs against main specs, and executing a safe timestamped relocation to the archive location.

Can I sync delta specs with main specs before archiving an OpenSpec change?▼

Yes, you can compare and optionally sync delta specs against main specs during the OpenSpec change archival workflow. This ensures spec updates are merged before the change directory is moved to the archive.

How does the completion check work when archiving an OpenSpec change?▼

The completion check reviews artifact status and task completion before archiving an OpenSpec change, surfacing unfinished work early to prevent premature archival of incomplete changes.

What happens if an existing archive already exists when archiving an OpenSpec change?▼

When an existing archive is present, the workflow applies a safe timestamped relocation to prevent overwriting. This ensures previous archived OpenSpec changes remain intact and historically tracked without data loss.