openspec-archive-change

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

1|Updated Aug 21, 2023
One-click install
npx skills add https://github.com/jmuchovej/homelab --skill openspec-archive-change-jmuchovej
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/jmuchovej/homelab/tree/main/.agents/skills/openspec-archive-change
Command: npx skills add https://github.com/jmuchovej/homelab --skill openspec-archive-change-jmuchovej

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 entire finalization sequence so nothing is archived prematurely or left out of sync. ## 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 unfinished work. - Delta spec sync assessment: Compares delta specs against main specs, optionally runs an inline sync workflow, and verifies the result before archiving. - Safe archiving: Moves the change directory into a date-prefixed archive folder, 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 spec deltas to the main specs, and moves the change to archive/2024-01-15-user-auth. ## Quick Start Archive the completed OpenSpec change named add-user-auth and sync its delta specs to 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 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 prefixed with the current date.

How to sync delta specs to main specs before archiving?

When delta specs exist, the Skill compares each delta against its main spec and prompts you to sync. Choosing sync runs the openspec-sync-specs workflow inline, then re-verifies every capability before the archive proceeds.

Can I archive an OpenSpec change with incomplete tasks?

Yes. Incomplete tasks or artifacts trigger a warning showing the counts, and you are asked to confirm. Archiving proceeds if you confirm; the warnings are noted in the final summary.

Does the archive workflow work with OpenSpec stores?

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

What happens if the archive target directory already exists?

The archive fails with an error before anything is moved. You are advised to rename the existing archive or use a different date, and the change directory remains untouched.