openspec-archive-change

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

5|Updated Mar 21, 2026
One-click install
npx skills add https://github.com/8007342/tillandsias --skill openspec-archive-change-8007342
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/8007342/tillandsias/tree/main/.opencode/skills/openspec-archive-change
Command: npx skills add https://github.com/8007342/tillandsias --skill openspec-archive-change-8007342

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Finalizing a completed change in an OpenSpec workflow involves several manual checks—artifact completion, task status, and delta spec synchronization—before the change directory can be safely moved to the archive. This Skill automates that verification and archival process so completed changes are closed out consistently without losing spec updates. ## Core Features & Use Cases - Completion Verification: Checks artifact status via openspec status --json and counts incomplete tasks in tasks.md, warning before archiving with open items. - Delta Spec Sync Assessment: Compares delta specs against main specs, optionally runs an inline sync merge, and verifies the result before archiving. - Store-Aware Archiving: Supports registered OpenSpec stores via --store <id> and moves the change directory into a date-prefixed archive folder. - Use Case: After finishing implementation of a user-auth change, ask the agent to archive it; the Skill confirms all artifacts are done, syncs spec deltas into the main specs, and moves the change to changes/archive/2025-01-15-user-auth. ## Quick Start Ask the agent to archive the completed change named add-user-auth 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?▼

Provide the change name or let the Skill infer it from context; it runs openspec status to check artifacts, verifies tasks, assesses delta spec sync state, then moves the change directory into a date-prefixed archive folder.

How does OpenSpec archive handle unsynced delta specs?▼

The Skill compares each delta spec against its main spec and prompts you to sync now or archive without syncing. If you choose sync, it runs an inline merge and re-verifies every capability before archiving.

Can I archive an OpenSpec change with incomplete tasks?▼

Yes. The Skill counts incomplete tasks marked with unchecked boxes, displays a warning with the count, and asks for confirmation. Archiving proceeds if you confirm despite the open items.

Does openspec archive work with registered stores?▼

Yes. If the work lives in a registered store, the Skill discovers store ids with openspec store list --json and passes --store <id> on all commands that read or write specs and changes.

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 not moved, so nothing is lost and you can retry after resolving the conflict.