openspec-archive-change

Name: openspec-archive-change
Availability: InStock
Author: Rock

Archive completed openspec changes into dated paths after validating artifacts and tasks.

Updated Mar 9, 2025

Search Tags:#workflow #archive #openspec #change-management #artifact-status #delta-specs

Ready to run

npx skills add https://github.com/rock-hu/vitamin-compose --skill openspec-archive-change-rock-hu

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/rock-hu/vitamin-compose/tree/main/.qwen/skills/openspec-archive-change
Command: npx skills add https://github.com/rock-hu/vitamin-compose --skill openspec-archive-change-rock-hu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill archives a completed openspec change by moving it from the active changes directory to a date-stamped archive path after validating artifact completion and task status.

Core Features & Use Cases

Archive completed changes: safely relocate an approved change to an archive path, preserving the original configuration.
Validate completion: automatically check artifact statuses and task completion before archiving.
Delta spec sync: assess and optionally sync delta specs against main specs to maintain traceability.
Preserve configuration: keep the .openspec.yaml alongside archived content for future reference.
Use Case: When a feature is implemented and verified, run this skill to finalize and store it for historical records.

Quick Start

Use the openspec-archive-change skill to archive a completed change after all artifacts and tasks are confirmed done.

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 for historical traceability?▼

To archive completed openspec changes, the skill validates artifact status via the openspec status command, assesses tasks in tasks.md, and moves the change to a date-stamped archive path at openspec/changes/archive/YYYY-MM-DD-<name>.

What is the process to validate artifact completion before archiving a change?▼

Validating artifact completion involves checking the openspec status command and assessing task completion in tasks.md. The skill also compares delta specs against main specs to ensure all experimental workflow artifacts are fully finalized before relocation.

Can I preserve the .openspec.yaml configuration file when archiving a change?▼

Yes, the skill preserves the .openspec.yaml file alongside the archived content. It safely relocates the approved change to the archive directory while keeping the original configuration intact for future historical reference.

How do I sync delta specs to main specs before finalizing an openspec change?▼

The skill assesses and optionally syncs delta specs against main specs during the archiving process. This maintains traceability by ensuring experimental workflow changes are accurately compared and reconciled before the change is finalized.

What happens if task statuses in tasks.md are not fully completed before archiving?▼

The archiving process strictly validates task completion in tasks.md before moving the change. If tasks are not confirmed done, the skill prevents the relocation to the date-stamped archive path to ensure only fully implemented and verified features are stored.