openspec-archive-change

Archive completed OpenSpec changes with date-stamped paths and metadata.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/CMajorChords/HydroMind --skill openspec-archive-change-cmajorchords
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/CMajorChords/HydroMind/tree/main/.agents/skills/openspec-archive-change
Command: npx skills add https://github.com/CMajorChords/HydroMind --skill openspec-archive-change-cmajorchords

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archive a completed change in the OpenSpec workflow to preserve a reproducible, auditable record after implementation.

Core Features & Use Cases

  • Prompt for change selection: If no change name is provided, prompt the user to choose from active changes using the openspec list to avoid archiving the wrong item.
  • Artifact and task validation: Check artifact completion and tasks status before archiving to ensure only finished work is archived.
  • Delta-spec assessment & optional sync: Analyze any delta specs against main specs and, if needed, run a sync to align documentation before archiving.
  • Archive relocation: Move the completed change into an archive directory named with a date prefix for traceability; preserve related metadata.

Quick Start

Finalize and archive a completed change by providing its name to the openspec-archive-change tool.

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 an OpenSpec change after implementation?

Archiving completed OpenSpec changes requires verifying artifact completion and task status, assessing delta-specs against main specs, and moving the change to a date-stamped archive path to preserve a reproducible historical record.

What is the process for archiving delta-specs in OpenSpec?

Archiving delta-specs involves assessing them against main specs to check alignment, optionally running a sync to update documentation, and then moving the completed change into a date-prefixed archive directory while preserving OpenSpec metadata.

How do I ensure only finished OpenSpec changes are archived?

To ensure only finished OpenSpec changes are archived, the workflow performs artifact completion and task status validation checks before executing the archive relocation to prevent archiving incomplete work.

Can I archive an OpenSpec change without specifying its name?

You can archive an OpenSpec change without specifying its name by prompting the tool to list active changes, allowing you to interactively select the correct item to avoid archiving the wrong experimental change.

Does OpenSpec archiving preserve the original change metadata?

OpenSpec archiving preserves the original change metadata by moving the completed change into a date-stamped archive directory, maintaining the OpenSpec schema for a reproducible and auditable historical record.