skills.rest
kuchida1981
kuchida1981COMMUNITY
Explore all skills by this author →
GitHub

openspec-archive-change

Archive completed openspec changes into the dated archive tree.

Updated Mar 4, 2026
Search Tags:#workflow#cli#archive#openspec#specs#change-management
One-click install
npx skills add https://github.com/kuchida1981/discord-service-gateway --skill openspec-archive-change-kuchida1981
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/kuchida1981/discord-service-gateway/tree/main/.gemini/skills/openspec-archive-change
Command: npx skills add https://github.com/kuchida1981/discord-service-gateway --skill openspec-archive-change-kuchida1981

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill finalizes a completed change by moving it into the archive history with the right checks, so teams can close work cleanly without losing context.

Core Features & Use Cases

  • Change Selection: Helps the user choose the correct active change when no name is supplied.
  • Completion Validation: Reviews artifact status, task completion, and delta spec sync state before archiving.
  • Safe Archiving: Creates the archive path, prevents name collisions, and moves the change directory into the dated archive location.
  • Use Case: Use it when an implementation is finished and you want to preserve the change in an organized archive while confirming nothing important is left unfinished.

Quick Start

Ask the openspec archive skill to archive the completed change you have finished and confirm any incomplete artifacts, tasks, or spec sync needs.

Frequently Asked Questions about openspec-archive-change

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I safely archive completed change management workflows without losing project metadata?▼

Safely archiving completed change workflows requires validating artifact status, verifying task completion, and syncing delta specs before moving the change directory into a dated archive tree to preserve all project metadata.

What is the best way to finalize an openspec change after implementation is finished?▼

Finalizing an openspec change involves running CLI status checks to review incomplete artifacts or tasks, selecting the correct active change, and executing a guarded move operation into a newly created archive directory.

Can I archive an active change if some delta specs are not synchronized?▼

Archiving an active change with unsynchronized delta specs triggers an optional synchronization step during the completion validation phase, allowing you to sync before executing the guarded directory move.

How do I prevent name collisions when moving multiple completed changes into the archive tree?▼

Preventing name collisions during archiving is handled by creating a dated archive path structure that isolates each finalized change directory, ensuring safe guarded move operations without overwriting existing project history.

Do I need to manually specify the change name when archiving completed specs?▼

Specifying the change name manually is not required; the system helps you choose the correct active change through CLI status checks when no name is supplied for the archiving operation.

Related Skills

Explore More Software Engineering Skills→
ywh0606ywh0606

opsx-verify

Verify OpenSpec changes for completion and readiness before archiving.

Community
Intermediate
jerome-benoitjerome-benoit
57

openspec-archive-change

Archive completed OpenSpec changes after validating artifacts and tasks.

Community
Advanced
MiDouTechMiDouTech

openspec-archive-change

Archive completed openspec changes into date-prefixed directories after verification.

Official
Advanced
CatsofsufferingCatsofsuffering
5

openspec-archive-change

Archive completed OpenSpec changes under openspec/changes/archive with status checks.

Community
Advanced