Openspec Archive Change
Finalize and move a completed OpenSpec change into the dated archive folder
Test report
- Verdict
- Works with setup
- Score
- Tested
- Jul 21, 2026
- Environment
- Claude Code 2.x (agent harness)
- Upstream re-checked
- Aug 10, 2026 · 74047c6
Cloned the repo, confirmed openspec CLI v1.7.0 is present, and ran the skill's commands (openspec list --json, openspec status --change) against the repo's real changes — all returned valid JSON. For OUTPUT I archived phase0-style-transfer-loop two ways in separate copies: baseline via native `openspec archive -y`, and skill-followed via its manual task/artifact checks + dated `mv`. `diff -rq` of the two resulting archive directories returned exit 0 (byte-identical, .openspec.yaml preserved in both), so the produced artifact is no better than baseline; the skill only adds confirmation gating and a summary. Security scan was clean, but SKILL.md Step 4 references invoking a `openspec-sync-specs` skill that returns 404 in this repo.
Scored on four weighted criteria — install, triggering, output vs. baseline, docs. How scoring works
- Installs cleanly 4/5
- Triggers reliably 5/5
- Output vs. baseline 5/10
- Docs & honesty 4/5
What Openspec Archive Change does
A Claude Code skill that archives a completed OpenSpec change: it lists active changes, checks artifact and task completion, assesses delta-spec sync state, then moves the change directory to openspec/changes/archive/YYYY-MM-DD-<name>. Triggers when the user says a change is done and wants to finalize or archive it. Requires the openspec CLI and an OpenSpec-initialized project.
How to install Openspec Archive Change
git clone --depth 1 https://github.com/VILA-Lab/FigMirror.git /tmp/openspec-archive-change-src
mkdir -p ~/.claude/skills
cp -R /tmp/openspec-archive-change-src/.claude/skills/openspec-archive-change ~/.claude/skills/openspec-archive-change
# Requires the openspec CLI on PATH: npm i -g openspec (verified against v1.7.0)
# Only functions inside an OpenSpec-initialized project (an openspec/changes/ tree). Run `openspec init` if absent.
# Note: skill Step 4 invokes a sibling skill `openspec-sync-specs` that is NOT in this repo (404); that path only runs when a change has delta specs under specs/.
Skills live in ~/.claude/skills/ (global) or .claude/skills/
(per-project). Restart Claude Code after installing.
Commands — how to trigger Openspec Archive Change
-
/openspec-archive-changeFinalize and move a completed OpenSpec change into the dated archive folder
It also activates on plain-language prompts like these:
-
Archive this completed OpenSpec change -
Finalize and file away this finished change -
Close out this OpenSpec change after merging
Frequently asked questions
- Is the Openspec Archive Change skill free?
- Yes. The skill itself is free from VILA-Lab/FigMirror. SkillProof publishes the install command and an independent test verdict at no cost.
- Does Openspec Archive Change work with Claude Code?
- We tested it with Claude Code 2.x (agent harness) on Jul 21, 2026. Verdict: Works with setup. Cloned the repo, confirmed openspec CLI v1.7.0 is present, and ran the skill's commands (openspec list --json, openspec status --change) against the repo's real changes — all returned valid JSON. For OUTPUT I archived phase0-style-transfer-loop two ways in separate copies: baseline via native `openspec archive -y`, and skill-followed via its manual task/artifact checks + dated `mv`. `diff -rq` of the two resulting archive directories returned exit 0 (byte-identical, .openspec.yaml preserved in both), so the produced artifact is no better than baseline; the skill only adds confirmation gating and a summary. Security scan was clean, but SKILL.md Step 4 references invoking a `openspec-sync-specs` skill that returns 404 in this repo.
- What is the Openspec Archive Change SkillProof Score?
- 7.2/10 — installs cleanly 4/5, triggers reliably 5/5, output vs. baseline 5/10, docs & honesty 4/5.
- How do I install Openspec Archive Change?
- Copy the install command from this page, run it in your terminal, and restart Claude Code. Skills live in ~/.claude/skills/ (global) or .claude/skills/ inside a project.
- Can I use Openspec Archive Change with Cursor, Copilot, Gemini CLI, Codex or other AI tools?
- The SKILL.md format is native to Claude (Claude Code, Desktop, claude.ai). The instructions inside adapt to other assistants: Cursor rules, GitHub Copilot instructions, Windsurf rules, Custom GPTs, AGENTS.md for OpenAI Codex, and GEMINI.md for Google Gemini CLI — our conversion guides cover each, and the free converter on the tools page does the wrapping for you.