openspec-archive-change

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

Updated Aug 10, 2026
One-click install
npx skills add https://github.com/neuthos/ldx-monorepo --skill openspec-archive-change-neuthos
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/neuthos/ldx-monorepo/tree/main/.agents/skills/openspec-archive-change
Command: npx skills add https://github.com/neuthos/ldx-monorepo --skill openspec-archive-change-neuthos

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 active change exists, 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 but not blocking on gaps. - Delta spec sync: Compares delta specs against main specs, optionally runs an inline agent-driven sync, and verifies the result before archiving. - Dated archival: 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 agent 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 and sync 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 the change name, or let it infer the change from context. The Skill checks artifact and task completion, optionally syncs delta specs into main specs, then moves the change directory into an archive folder with a YYYY-MM-DD prefix.

How do I archive an OpenSpec change in a specific store?▼

Run openspec store list --json to discover registered store ids, then the Skill appends --store <id> to every openspec command that reads or writes specs and changes. The selected store flag stays sticky for the rest of the workflow.

Can I archive a change with incomplete tasks or artifacts?▼

Yes, archiving is not blocked by incomplete items. The Skill displays a warning listing incomplete artifacts or the count of unchecked tasks and asks for confirmation before proceeding.

What happens if delta specs are not synced before archiving?▼

The Skill compares each delta spec against its main spec and shows a combined summary. You can choose to sync first, archive without syncing, or cancel; if a sync runs, the result is verified before the change is moved.

Why does archiving fail when the target directory already exists?▼

The archive target is named YYYY-MM-DD-<change-name>, and the Skill refuses to overwrite an existing directory with that name. Rename the existing archive or use a different date to resolve the conflict.