openspec-archive-change

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

1|Updated Apr 9, 2026
One-click install
npx skills add https://github.com/CoderCoco-Studios/Hyveon --skill openspec-archive-change-codercoco-studios
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/CoderCoco-Studios/Hyveon/tree/main/.claude/skills/openspec-archive-change
Command: npx skills add https://github.com/CoderCoco-Studios/Hyveon --skill openspec-archive-change-codercoco-studios

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 a dated archive. This Skill automates that entire finalization sequence with the openspec CLI. ## Core Features & Use Cases - Guided change selection: Infers the change from context, auto-selects when only one is active, 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 before proceeding. - Delta spec sync: Compares delta specs against main specs, optionally runs an inline intelligent merge, and verifies the result before archiving. - Dated archiving: Moves the change directory into an archive folder with a YYYY-MM-DD- prefix, refusing to overwrite existing archives. - Use Case: After finishing implementation of a feature change, ask the assistant to archive it; the Skill validates everything, syncs specs if needed, and produces a summary of what was archived. ## 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 OpenSpec change?

Invoke the archive workflow with a 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 an 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 the tasks file and displays a warning with the count. It asks for confirmation before proceeding, so archiving is never blocked but you are informed of incomplete work.

Does the archive workflow sync delta specs to main specs?

Yes, when delta specs exist it compares them against main specs and prompts you to sync first or archive without syncing. If you choose sync, it runs an inline merge and verifies every capability before moving the change.

Can I archive a change stored in a named OpenSpec store?

Yes, run `openspec store list --json` to discover registered store ids, then pass `--store <id>` on commands that read or write specs and changes. Without a store flag, commands act on the nearest local openspec root.

What happens if the archive target directory already exists?

The archive fails with an error rather than overwriting. The Skill suggests renaming the existing archive or using a different date, and it never stacks a second date prefix on an already dated change name.