openspec-archive-change

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

Updated Aug 7, 2026
One-click install
npx skills add https://github.com/javakishore-veleti/lifting-diary-app --skill openspec-archive-change-javakishore-veleti
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/javakishore-veleti/lifting-diary-app/tree/main/.qwen/skills/openspec-archive-change
Command: npx skills add https://github.com/javakishore-veleti/lifting-diary-app --skill openspec-archive-change-javakishore-veleti

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 - Completion verification: Checks artifact status via openspec status --json and counts incomplete tasks in tasks.md before archiving, 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 merge before moving anything. - 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 user-auth change, ask the assistant to archive it; the Skill confirms all artifacts are done, syncs the spec deltas, and moves the change to the archive with a summary. ## 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 verifies 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 archiving sync delta specs to main specs automatically?

Only if the user chooses the sync option when prompted. The Skill compares delta specs with main specs, shows a combined summary, and offers choices including syncing now or archiving without syncing.

Can I archive a change in a specific OpenSpec store?

Yes. Run `openspec store list --json` to discover registered store ids, then the Skill passes `--store <id>` on all commands that read or write specs and changes, treating it as sticky for the 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 moved or overwritten when a name collision occurs.