skills.rest
hmj1026
hmj1026COMMUNITY
Explore all skills by this author →
GitHub

openspec-archive-change

Archive completed OpenSpec changes into dated directories with optional delta synchronization.

Updated Nov 26, 2025
Search Tags:#workflow#archive#openspec#delta#artifact#specs#change
One-click install
npx skills add https://github.com/hmj1026/docker_run --skill openspec-archive-change-hmj1026
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/hmj1026/docker_run/tree/main/.gemini/skills/openspec-archive-change
Command: npx skills add https://github.com/hmj1026/docker_run --skill openspec-archive-change-hmj1026

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archive a completed change in the OpenSpec workflow to preserve a reproducible record and prevent rework after implementation.

Core Features & Use Cases

  • Validate artifact and task completion before archiving.
  • Compare delta specs with main specs and optionally synchronize to maintain consistency.
  • Create a dated archive directory and move the change under openspec/changes/archive/YYYY-MM-DD-<name> while preserving .openspec.yaml.
  • Preserve metadata and summary by generating an archive record and a clear completion summary.
  • Prompt for change selection when not provided.

Quick Start

Provide the change name to archive, and the tool will guide you through verification, optional syncing, and safe relocation 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 completed changes in OpenSpec?▼

Archive OpenSpec changes by providing the change name for the tool to guide you through artifact verification, optional delta spec syncing, and safe relocation to a dated openspec/changes/archive/YYYY-MM-DD-<name> directory.

What happens to delta specs when archiving an OpenSpec change?▼

The tool compares delta specs with main specs during archiving and optionally synchronizes them to maintain consistency, ensuring finished changes do not leave conflicting spec differences behind.

Does the OpenSpec archiving process require any specific CLI tools?▼

Yes, the archiving process requires the OpenSpec CLI to validate artifact completion checks and safely move finished changes to the openspec/changes/archive directory while preserving the .openspec.yaml file.

Why should I archive completed OpenSpec changes instead of deleting them?▼

Archiving completed OpenSpec changes preserves a reproducible record and prevents rework after implementation by generating an archive record and a clear completion summary in a dated archive directory.

Can I archive an OpenSpec change without knowing the exact change name?▼

Yes, when the change name is not provided, the tool prompts you for change selection interactively, guiding you through artifact verification, optional syncing, and safe relocation to the archive.

Related Skills

Explore More Software Engineering Skills→
shivrosshivros

openspec-archive-change

Archive completed changes in the experimental workflow using the openspec CLI.

Community
Intermediate
goerngoern
113

openspec-archive-change

Archive completed OpenSpec changes into dated directories with validation.

Community
Advanced
Pony-UnicornPony-Unicorn
7

openspec-archive-change

Archive completed openspec changes after verifying artifact and task status.

Community
Advanced
jrmatherlyjrmatherly

openspec-archive-change

Archive completed openspec change directories after validating artifacts and tasks.

Community
Advanced