opsx-archive

Archives completed changes from openspec/changes into a dated folder with pre-checks.

Updated Jan 20, 2026

Search Tags:#workflow #archive #openspec #change-management #delta-spec #artifact-status

Ready to run

npx skills add https://github.com/moogah/emacs --skill opsx-archive-moogah

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: opsx-archive
Source: https://github.com/moogah/emacs/tree/main/.claude/skills/opsx-archive
Command: npx skills add https://github.com/moogah/emacs --skill opsx-archive-moogah

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archive completed changes from the active openspec/changes directory into a centralized archive, ensuring a traceable record of finalized work.

Core Features & Use Cases

Saves artifacts by moving the change directory to openspec/changes/archive/YYYY-MM-DD-<name> and preserving the .openspec.yaml file.
Performs pre-archive checks for artifact completion, open tasks, and delta spec synchronization, prompting for confirmation when needed.
Provides a clear summary of the archive status, including the archive location and any warnings.

Quick Start

Specify the change name to begin archiving and follow the prompts to complete the process.

Frequently Asked Questions about opsx-archive

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

FAQPage Schema

How do I archive completed OpenSpec changes from the active directory?▼

Archiving completed changes involves moving the change directory from openspec/changes to a date-based archive path, preserving the .openspec.yaml file to maintain a traceable record of finalized work.

What happens if my delta specs are not synchronized before archiving?▼

Before archiving, pre-archive checks verify artifact completion and delta spec synchronization; if checks fail, the process prompts for confirmation rather than proceeding silently.

Can I archive multiple changes without specifying a name?▼

Explicit change selection is required to archive changes; the process needs a specified change name to move the correct directory and generate a concise summary of the archival result.

How does date-based archiving prevent directory conflicts?▼

Date-based archiving prevents conflicts by generating a unique openspec/changes/archive/YYYY-MM-DD-<name> path, ensuring each archived change directory remains distinct without overwriting previous records.

What does the archival summary include when moving changes?▼

The archival summary includes the archive location and any warnings, providing a clear status of the operation after moving the change directory and verifying artifact completion.