openspec-archive-change

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

Updated Aug 5, 2026
One-click install
npx skills add https://github.com/JhonMA82/api-starter --skill openspec-archive-change-jhonma82
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/JhonMA82/api-starter/tree/main/.opencode/skills/openspec-archive-change
Command: npx skills add https://github.com/JhonMA82/api-starter --skill openspec-archive-change-jhonma82

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Finalizing a spec-driven change involves many manual checks: confirming artifacts are done, tasks are complete, delta specs are merged into main specs, and the change directory is moved to a dated archive. This Skill automates that entire finalization workflow through the OpenSpec CLI so nothing is archived prematurely or left unsynced. ## 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 archiving with open items. - Delta spec sync: Compares delta specs against main specs, optionally runs an inline intelligent merge, and verifies the result 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 verifies all artifacts and tasks, syncs the delta specs into the main specs, and moves the change to changes/archive/2025-01-15-user-auth/. ## Quick Start Archive the completed OpenSpec change named add-user-auth, syncing 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 OpenSpec change?▼

Invoke the archive workflow with a change name or let it infer one from context. It checks artifact and task completion, optionally syncs delta specs into main specs, then moves the change directory into a dated archive folder.

How to sync delta specs into main specs before archiving?▼

The workflow compares each delta spec against its main spec, shows a combined summary, and offers a sync option. Choosing sync runs an inline agent-driven merge, then re-verifies every capability before archiving proceeds.

Can I archive an OpenSpec change with incomplete tasks?▼

Yes, but with a warning. The workflow counts incomplete tasks marked with unchecked boxes and asks for confirmation before proceeding. The final summary notes how many tasks were left incomplete.

Does the archive workflow work with OpenSpec stores?▼

Yes. If the work lives in a registered store, it discovers store ids via openspec store list and passes the --store flag on all spec and change commands, keeping it sticky for the rest of the workflow.

What happens if the spec sync fails during archiving?▼

The workflow stops without archiving. The change directory remains untouched, and it reports which capabilities still differ so you can fix the mismatch or re-run the sync before archiving again.