skills.rest
leoszr
leoszrCOMMUNITY
Explore all skills by this author →
GitHub

openspec-archive-change

Archive completed OpenSpec changes after validating artifacts and tasks.

Updated Jun 20, 2026
Search Tags:#workflow#archive#status#archiving#openspec#change-management#delta-specs
One-click install
npx skills add https://github.com/leoszr/finance-app --skill openspec-archive-change-leoszr
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/leoszr/finance-app/tree/main/.opencode/skills/openspec-archive-change
Command: npx skills add https://github.com/leoszr/finance-app --skill openspec-archive-change-leoszr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archive completed OpenSpec changes in the experimental workflow, enabling finalization, validation of artifacts and tasks, and preservation of history.

Core Features & Use Cases

  • Interactive change selection: prompts the user to pick an active change for archiving.
  • Artifact & task validation: checks status of artifacts via openspec status and tasks in tasks.md.
  • Delta-spec assessment: compares delta specs to main specs and guides syncing decisions.
  • Safe archiving: moves the change to openspec/changes/archive/YYYY-MM-DD-<name> while preserving important config files.
  • Optional syncing: can perform delta-spec synchronization during archiving.

Quick Start

Initiate the archive flow for a selected change and follow prompts to validate artifacts, confirm tasks, and optionally sync delta specs before archiving.

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 changes with delta-spec synchronization?▼

To archive completed OpenSpec changes, initiate the archive flow to validate artifacts and tasks via openspec status, optionally sync delta specs to main specs, and move the change to openspec/changes/archive/YYYY-MM-DD-<name> while preserving history.

What does OpenSpec change archiving validate before relocation?▼

OpenSpec change archiving validates artifact status using openspec status and checks task completion in tasks.md. It also assesses delta specs by comparing them to main specs to guide synchronization decisions before safely moving the change.

Do I need the OpenSpec CLI to archive changes in the experimental workflow?▼

Yes, archiving changes requires the OpenSpec CLI and local project state to execute status checks, perform delta comparisons, and finalize the move operations to the archive directory.

How to sync delta specs to main specs during OpenSpec change archiving?▼

During the archiving process, the Skill compares delta specs against main specs and guides syncing decisions. You can optionally perform delta-spec synchronization before the change is moved to the archive folder.

What is preserved when archiving an OpenSpec change to the archive directory?▼

When archiving an OpenSpec change, the process moves the change to openspec/changes/archive/YYYY-MM-DD-<name> while preserving important configuration files and maintaining archive history for future reference.

Related Skills

Explore More Software Engineering Skills→
alexei-lexxalexei-lexx

openspec-verify-change

Validate alignment between openspec change artifacts and implemented code.

Community
Advanced
Alex1980AlexAlex1980Alex

openspec-archive-change

Archive completed OpenSpec changes into dated directories after completion checks.

Community
Advanced
DataCoveyDataCovey
27

openspec-archive-change

Archive a completed OpenSpec change to preserve artifacts and align with the experimental workflow.

Official
Advanced
lbrlabslbrlabs
9

openspec-archive-change

Archive completed OpenSpec changes under openspec/changes/archive with metadata preservation.

Official
Advanced