skills.rest
sachinnair90
sachinnair90COMMUNITY
Explore all skills by this author →
GitHub

openspec-archive-change

Archive completed OpenSpec changes after validating status and task completion.

Updated Apr 3, 2026
Search Tags:#workflow#validation#archive#change management#openspec#spec sync
One-click install
npx skills add https://github.com/sachinnair90/gitgloss --skill openspec-archive-change-sachinnair90
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/sachinnair90/gitgloss/tree/main/.claude/skills/openspec-archive-change
Command: npx skills add https://github.com/sachinnair90/gitgloss --skill openspec-archive-change-sachinnair90

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the manual overhead of closing out a completed OpenSpec change by guiding the archive process, checking readiness, and handling the move into archive history safely.

Core Features & Use Cases

  • Change Selection: Helps identify the correct active change when the user does not provide a clear name.
  • Completion Validation: Checks artifact status and task progress before archiving, warning when anything remains unfinished.
  • Delta Spec Review: Compares delta specs against main specs and lets the user decide whether to sync before archiving.
  • Safe Archiving: Moves the change into a dated archive path while preserving the change’s metadata and structure.
  • Use Case: A developer has finished implementing a workflow change and wants to confirm readiness, sync any outstanding spec updates, and archive it in a consistent location.

Quick Start

Ask the skill to archive the completed change named <change-name>, and let it verify readiness, offer syncing if needed, and move it into 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 safely archive a completed OpenSpec change?▼

To archive a completed OpenSpec change, the workflow validates artifact status, confirms task completion, optionally syncs delta specs, and moves the change into dated archive storage while preserving metadata.

What does the OpenSpec change archiving process check before finalizing?▼

The OpenSpec change archiving process checks artifact status via JSON inspection and reviews task-file completion to ensure all workflow tasks are finished before moving the change to archive history.

Can I sync delta specs with main specs before archiving an OpenSpec change?▼

Yes, the archiving workflow compares delta specs against main specs and prompts the user to decide whether to synchronize outstanding spec updates before moving the change into the archive.

How do I clean up inactive OpenSpec changes without losing metadata?▼

Inactive OpenSpec changes are cleaned up using safe filesystem move operations that transfer the change into a dated archive path while preserving the change's original metadata and directory structure.

What happens if I try to archive an OpenSpec change with incomplete tasks?▼

If task-file review reveals incomplete items during the archiving process, the workflow issues a warning about unfinished artifacts and requires user confirmation before proceeding to archive storage.

Related Skills

Explore More Software Engineering Skills→
ywh0606ywh0606

opsx-verify

Verify OpenSpec changes for completion and readiness before archiving.

Community
Intermediate
eburairueburairu
1

sdd-archive

Move completed spec directories to dated archive paths under .sdd/specs/archives/.

Community
Basic
jankneumannjankneumann
4

openspec-archive-change

Archive completed OpenSpec change directories to a dated location.

Community
Advanced
kuchida1981kuchida1981

openspec-archive-change

Archive completed openspec changes into the dated archive tree.

Community
Advanced