openspec-archive-change

Archive completed OpenSpec changes with artifact and task validation.

2|Updated Feb 5, 2026
One-click install
npx skills add https://github.com/dshearer/misatay --skill openspec-archive-change-dshearer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/dshearer/misatay/tree/main/.claude/skills/openspec-archive-change
Command: npx skills add https://github.com/dshearer/misatay --skill openspec-archive-change-dshearer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archive completed changes in the experimental OpenSpec workflow.

Core Features & Use Cases

  • Archive completed changes from the experimental workflow after implementation is complete.
  • Validate artifact and task statuses, delta-spec synchronization, and archiving with a date-stamped archive path.
  • Use case: safely finalize changes and preserve history for audits and traceability.

Quick Start

Archive a completed change using the openspec-archive-change skill to move it into the archive folder and optionally sync delta specs.

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 change workflows and preserve traceability?

To archive completed change workflows, you validate artifact and task completion statuses, synchronize delta specs, and move the change to a date-stamped archive path. This ensures reproducibility and traceability for future audits.

What is delta-spec synchronization in change management archival?

Delta-spec synchronization in change management ensures that incremental specification updates are aligned before a change is archived. It validates that all modified artifacts are consistent and properly recorded within the archive structure.

What's the best way to safely finalize changes in the OpenSpec workflow?

The best way to safely finalize changes in the OpenSpec workflow is to run an archival process that enforces completion checks and prompts. This applies safeguards and organizes artifacts into a structured archive path for safekeeping.

Do I need to validate task completion before archiving OpenSpec changes?

Yes, you need to validate task and artifact completion statuses before archiving OpenSpec changes. The workflow enforces these checks to ensure that all implementation requirements are met before the change is moved to the archive.

Why does my change management archive require a date-stamped path?

A change management archive requires a date-stamped path to ensure reproducibility and traceability. It provides a structured organization that allows you to locate and audit historical changes accurately over time.