skills.rest
feidon
feidonCOMMUNITY
Explore all skills by this author →
GitHub

openspec-archive-change

Archives completed OpenSpec changes after verifying artifact and task completion.

Updated Mar 30, 2026
Search Tags:#cli#archive#change management#openspec#task verification#spec workflow
One-click install
npx skills add https://github.com/feidon/vss --skill openspec-archive-change-feidon
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/feidon/vss/tree/main/frontend/.claude/skills/openspec-archive-change
Command: npx skills add https://github.com/feidon/vss --skill openspec-archive-change-feidon

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Finalizing a completed change in an OpenSpec workflow involves checking artifact status, verifying task completion, syncing delta specs, and moving directories, which is error-prone when done manually. ## Core Features & Use Cases - Completion Verification: Checks artifact status via openspec status --json and counts incomplete tasks in tasks.md before archiving. - Delta Spec Sync Assessment: Compares delta specs against main specs and optionally triggers a sync subagent before archiving. - Safe Archiving: Moves the change directory to openspec/changes/archive/YYYY-MM-DD-<name> with collision detection. - Use Case: After finishing implementation of a feature change, ask the assistant to archive it; the skill prompts you to confirm any incomplete artifacts or tasks, syncs specs if needed, and archives the change with a dated folder name. ## Quick Start Archive the completed change named add-user-auth and sync its delta specs before moving it to 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 archive a completed OpenSpec change?▼

Invoke the archive workflow with a change name, or let it list active changes via `openspec list --json` so you can select one. It verifies completion, optionally syncs delta specs, then moves the directory to openspec/changes/archive with a date prefix.

What happens if tasks are incomplete when archiving a change?▼

The skill counts incomplete tasks marked with `- [ ]` in tasks.md and displays a warning with the count. It asks for confirmation before proceeding, so archiving is never blocked but you stay informed.

Does archiving a change require the openspec CLI?▼

Yes, the workflow requires the openspec CLI to list changes and check artifact completion status via `openspec status --json`. The actual archive move uses standard shell commands like mkdir and mv.

What happens if the archive target directory already exists?▼

The archive fails with an error if a folder named YYYY-MM-DD-<change-name> already exists in openspec/changes/archive. You are advised to rename the existing archive or use a different date.

Can I archive a change without syncing delta specs?▼

Yes. When delta specs exist, the skill shows a summary of pending changes and lets you choose between syncing first or archiving without syncing. Archiving proceeds regardless of your choice.

Related Skills

Explore More Software Engineering Skills→
MiDouTechMiDouTech

openspec-archive-change

Archive completed openspec changes into date-prefixed directories after verification.

Official
Advanced
ValyntValynt

openspec-archive-change

Archive completed changes with artifact checks and optional delta-spec sync.

Official
Advanced
cynkracynkra
1

openspec-sync-specs

Merge delta OpenSpec requirement blocks into main spec files per capability.

Official
Intermediate
prime-radiant-incprime-radiant-inc
91

executing-plans

Execute implementation plans in controlled batches with review checkpoints.

Official
Advanced