openspec-archive-change

Archive completed OpenSpec changes after validating artifacts and tasks.

Updated Jun 9, 2026
One-click install
npx skills add https://github.com/hellyaxs/case-cell-shop --skill openspec-archive-change-hellyaxs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/hellyaxs/case-cell-shop/tree/main/.cursor/skills/openspec-archive-change
Command: npx skills add https://github.com/hellyaxs/case-cell-shop --skill openspec-archive-change-hellyaxs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps users finalize completed OpenSpec changes by validating completion status, handling synchronization decisions, and moving finished work into an archive without losing workflow context.

Core Features & Use Cases

  • Change Archiving Workflow: Guides the process of selecting changes, checking artifacts and tasks, and creating dated archive locations.
  • Completion Validation: Reviews artifact status, unfinished tasks, and delta specification synchronization before archiving.
  • Use Case: A developer finishing an OpenSpec implementation can use this Skill to verify readiness, resolve warnings, and archive the completed change with a clear summary.

Quick Start

Use the openspec-archive-change skill to archive the completed OpenSpec change after verifying its artifacts and tasks.

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 OpenSpec workflow changes?

Validate completion status by reviewing artifact validation, checking unfinished tasks, and verifying delta specification synchronization, then move the finished OpenSpec change into a dated archive location to preserve workflow metadata.

What is the process for validating OpenSpec change readiness before archiving?

Validating OpenSpec change readiness involves checking artifact status, resolving unfinished tasks, and verifying delta specification synchronization to ensure implementation completion before archiving.

Does the OpenSpec change archiving workflow require the openspec CLI?

Yes, archiving OpenSpec changes requires the openspec CLI to inspect change status, manage archives, and preserve workflow metadata during the finalization of completed workflow changes.

Why should I archive completed OpenSpec changes instead of leaving them active?

Archiving completed OpenSpec changes moves finished work into structured archives without losing workflow context, keeping active workspaces clean while preserving task completion checks and artifact validation records.

Can I archive an OpenSpec change with unfinished tasks or unresolved warnings?

You should resolve unfinished tasks and warnings first, because the archiving process validates implementation readiness by checking artifact status and delta specification synchronization before moving changes into the archive.