openspec-archive-change

Archives completed OpenSpec changes after verifying artifacts, tasks, and spec sync state.

Updated Jun 13, 2026
One-click install
npx skills add https://github.com/anionDevelopment/Epew --skill openspec-archive-change-aniondevelopment
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/anionDevelopment/Epew/tree/main/.opencode/skills/openspec-archive-change
Command: npx skills add https://github.com/anionDevelopment/Epew --skill openspec-archive-change-aniondevelopment

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Finalizing a completed change in an OpenSpec workflow involves checking artifact completion, task status, and delta spec synchronization before moving the change into an archive directory. Doing this manually is error-prone and can leave main specs out of sync with the change. ## Core Features & Use Cases - Guided change selection: Infers the change from context, auto-selects when only one active change exists, or prompts with a list of active changes when ambiguous. - Completion verification: Checks artifact status via openspec status --json and counts incomplete tasks in tasks.md, warning but not blocking on gaps. - Delta spec sync assessment: Compares delta specs against main specs, optionally runs an inline sync workflow, and verifies the result before archiving. - Use Case: After finishing implementation of a user-auth change, ask the assistant to archive it; the skill validates artifacts and tasks, syncs specs if needed, and moves the change to archive/YYYY-MM-DD-user-auth. ## Quick Start Ask the assistant to archive the completed change named add-user-auth using the openspec archive workflow.

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 change in OpenSpec?▼

Provide the change name or let the skill infer it from context. It checks artifact and task completion, assesses delta spec sync state, then moves the change directory into an archive folder with a YYYY-MM-DD prefix.

What happens if tasks are incomplete when archiving an OpenSpec change?▼

The skill counts incomplete tasks marked with `- [ ]` in tasks.md and displays a warning with the count. It asks for confirmation but does not block the archive, proceeding once the user confirms.

Does the archive workflow sync delta specs to main specs?▼

Yes, when delta specs exist it compares them against main specs and prompts to sync. If sync is chosen, it runs the openspec-sync-specs workflow inline and verifies every capability before archiving.

Can I archive a change in a registered OpenSpec store?▼

Yes, run `openspec store list --json` to discover store ids, then pass `--store <id>` on commands that read or write specs and changes. The flag stays sticky for the rest of the workflow.

Why does archiving fail with a target already exists error?▼

The archive target name is the change name with a YYYY-MM-DD date prefix, and the move fails if that directory already exists in the archive folder. Rename the existing archive or use a different date to resolve it.