openspec-archive-change

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

Updated Jul 1, 2025
One-click install
npx skills add https://github.com/mosakuzii0216/mosaku-v1 --skill openspec-archive-change-mosakuzii0216
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/mosakuzii0216/mosaku-v1/tree/main/.claude/skills/openspec-archive-change
Command: npx skills add https://github.com/mosakuzii0216/mosaku-v1 --skill openspec-archive-change-mosakuzii0216

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Finalizing a completed change in an OpenSpec workflow involves several manual checks: confirming artifacts are done, verifying tasks are complete, syncing delta specs into main specs, and moving the change directory into an archive. This Skill automates that entire finalization sequence through the openspec CLI. ## 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: Compares delta specs against main specs, optionally runs an inline sync workflow, and verifies the merge before archiving. - Safe archiving: Moves the change directory into a date-prefixed archive folder, failing safely if the target already exists. - Use Case: After finishing implementation of a user-auth change, ask the assistant to archive it; the Skill verifies all artifacts, syncs spec deltas, and moves the change to changes/archive/2025-01-15-user-auth. ## Quick Start Archive the completed OpenSpec change named add-user-auth and sync its delta specs into the main specs first.

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?

Invoke the archive workflow with a change name or let it be inferred from context. The Skill checks artifact and task completion, optionally syncs delta specs to main specs, then moves the change directory into a date-prefixed archive folder.

How to sync delta specs to main specs before archiving?

The Skill compares each delta spec against its main spec and prompts you to sync. If confirmed, it runs the openspec-sync-specs workflow inline, then re-verifies every capability before moving the change to the archive.

Can I archive a change with incomplete tasks in OpenSpec?

Yes. The Skill counts incomplete tasks marked with unchecked boxes and warns you, but only asks for confirmation rather than blocking. The same applies to artifacts that are neither done nor skipped.

Does openspec archive work with named stores?

Yes. If the work lives in a registered store, the Skill runs openspec store list --json to discover store ids and passes --store <id> on all commands that read or write specs and changes for the rest of the workflow.

What happens if the archive target directory already exists?

The archive fails with an error before moving anything. The Skill suggests renaming the existing archive or using a different date, leaving the change directory untouched so you can retry safely.