openspec-archive-change

Validate artifact status and task completion before archiving openspec experimental changes.

3|2|Updated Aug 1, 2025
One-click install
npx skills add https://github.com/ClearMeasureLabs/bootcamp-palermo-workorders --skill openspec-archive-change-clearmeasurelabs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/ClearMeasureLabs/bootcamp-palermo-workorders/tree/main/.cursor/skills/openspec-archive-change
Command: npx skills add https://github.com/ClearMeasureLabs/bootcamp-palermo-workorders --skill openspec-archive-change-clearmeasurelabs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of managing the lifecycle of experimental workflow changes by ensuring they are properly validated, synced, and archived without leaving behind incomplete tasks or artifacts.

Core Features & Use Cases

  • Validation Checks: Automatically verifies that all artifacts are marked as done and all tasks are completed before archiving.
  • Delta Spec Synchronization: Compares experimental delta specs against main specifications and provides a guided sync process.
  • Use Case: After completing a feature implementation in an experimental branch, use this Skill to ensure all documentation is updated and the change is moved to the archive directory with a timestamped record.

Quick Start

Use the openspec-archive-change skill to finalize the current change named feature-x and move it to the 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 experimental changes and sync delta specifications with main documentation?

To archive experimental changes, you validate artifact status and task completion, then sync delta specifications with main documentation before moving directories to a timestamped archive.

What is the best way to finalize an experimental workflow change without leaving incomplete artifacts?

Finalizing an experimental workflow change requires automated validation checks to ensure all artifacts are marked done and tasks are completed before archiving.

Do I need the openspec CLI to validate task completion before archiving?

Yes, the openspec CLI is required to perform status checks and file system operations for validating artifact status and task completion during the archiving process.

How does delta spec synchronization work when archiving completed feature implementations?

Delta spec synchronization compares experimental delta specs against main specifications and provides a guided sync process to update documentation before archiving.

Can I archive incomplete experimental changes with unfinished tasks?

No, the archiving process validates that all artifacts are marked as done and all tasks are completed before moving experimental changes to the archive.