openspec-archive-change

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

Updated Sep 16, 2026
One-click install
npx skills add https://github.com/JoeShi/coding-agent-usage-montior --skill openspec-archive-change-joeshi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/JoeShi/coding-agent-usage-montior/tree/main/.kimi-code/skills/openspec-archive-change
Command: npx skills add https://github.com/JoeShi/coding-agent-usage-montior --skill openspec-archive-change-joeshi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Finalizing a completed change in an OpenSpec workflow involves several error-prone manual checks: confirming artifacts are done, verifying tasks are complete, syncing delta specs into main specs, and moving the change directory into the archive with a correct date prefix. This Skill automates that entire finalization sequence through the openspec CLI. ## Core Features & Use Cases - Completion Verification: Checks artifact status via openspec status --json and counts incomplete tasks in tasks.md, warning before archiving unfinished work. - Delta Spec Sync Assessment: Compares delta specs against main specs, optionally runs the openspec-sync-specs merge inline, and verifies the result before archiving. - Store-Aware Archiving: Supports registered OpenSpec stores via --store <id>, creates the archive directory, applies YYYY-MM-DD- date prefixes, and prevents duplicate archive targets. - Use Case: After finishing implementation of a change like add-codex-cli-support, ask the assistant to archive it; the Skill validates completion, syncs specs if needed, moves the change into changes/archive/, and prints a summary. ## Quick Start Ask the assistant to archive the completed OpenSpec change named add-codex-cli-support and confirm any warnings about incomplete tasks.

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 the change name, or let it be inferred from context. The Skill checks artifact and task completion, assesses delta spec sync state, then moves the change directory into the archive folder with a YYYY-MM-DD 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 with incomplete tasks is allowed but never silent.

Does the archive workflow sync delta specs into main specs?

Yes. If delta specs exist, it compares them against main specs, shows a summary, and offers to sync. The sync runs inline via the openspec-sync-specs workflow and is re-verified before the change is moved.

Can I archive a change in a registered OpenSpec store?

Yes. Run `openspec store list --json` to discover store ids, then all read and write commands use `--store <id>`. The flag stays sticky for the rest of the archive workflow.

What happens if the archive target directory already exists?

The archive fails with an error suggesting you rename the existing archive or use a different date. The change directory is never overwritten or partially moved.