skills.rest
terry90918
terry90918COMMUNITY
Explore all skills by this author →
GitHub

openspec-archive-change

Moves a completed change into a dated archive after validating its artifacts and tasks.

Updated Aug 23, 2026
Search Tags:#workflow#versioning#cli#archive#openspec#change-management
One-click install
npx skills add https://github.com/terry90918/horse-blessing-2026 --skill openspec-archive-change-terry90918
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/terry90918/horse-blessing-2026/tree/main/.claude/skills/openspec-archive-change
Command: npx skills add https://github.com/terry90918/horse-blessing-2026 --skill openspec-archive-change-terry90918

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archive completed changes in the OpenSpec workflow to keep a clear, auditable history and prevent manual archiving errors.

Core Features & Use Cases

  • End-to-end archiving for completed changes with artifact and task validation prompts, optional delta-spec syncing assessment, and safe archival placement.
  • Guardrails ensure user confirmation for critical steps, preserving metadata and preventing data loss during archiving.
  • Use case: after finalizing a change, archive it to openspec/changes/archive/YYYY-MM-DD-<name> while maintaining compatibility with main specs.

Quick Start

Provide a change name when prompted and confirm the archive action to move the change into the archive folder.

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 without losing metadata?▼

To archive completed changes in OpenSpec safely, the workflow prompts you to select the change, verify artifact and task completion via openspec status, and move the directory to a dated archive folder while preserving all metadata.

What is the process for finalizing an OpenSpec change workflow?▼

Finalizing an OpenSpec change workflow involves prompting for change selection, validating artifacts and tasks are complete, optionally syncing delta specs, and moving the finalized change to a dated archive directory.

Does the OpenSpec archive process validate task completion before archiving?▼

Yes, the OpenSpec archive process enforces guardrails by prompting for user confirmation and validating artifacts through openspec status to ensure tasks are completed before safely moving the change directory to the archive.

Can I sync delta specs when archiving an OpenSpec change?▼

Yes, you can optionally assess and sync delta specs during the OpenSpec archiving process to maintain compatibility with main specs before the change directory is moved to the dated archive.

Why do I need to confirm change selection during OpenSpec archiving?▼

Confirming change selection during OpenSpec archiving acts as a guardrail to prevent manual archiving errors and data loss, ensuring the correct completed change is finalized, validated, and safely stored.

Related Skills

Explore More Software Engineering Skills→
esneiderbravoesneiderbravo
1

openspec-archive-change

Archive completed OpenSpec changes into a date-stamped directory with status checks.

Community
Advanced
statick88statick88
1

sdd-archive

Merge delta specifications into main specs and archive completed change folders.

Community
Advanced
rick2047rick2047

openspec-archive-change

Archive completed OpenSpec changes with finalized delta specs and artifacts.

Community
Advanced
ev3rlitev3rlit

gsd-cleanup

Archive completed milestone phase directories into versioned .planning paths.

Community
Intermediate