openspec-archive-change

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

Updated Sep 7, 2026
One-click install
npx skills add https://github.com/raphaelmans/spectralpointengineering --skill openspec-archive-change-raphaelmans
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/raphaelmans/spectralpointengineering/tree/main/.skillshare/skills/openspec-archive-change
Command: npx skills add https://github.com/raphaelmans/spectralpointengineering --skill openspec-archive-change-raphaelmans

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Finalizing a completed change in an OpenSpec workflow involves checking artifact completion, task status, and delta spec synchronization before moving the change into an archive directory; doing this manually is error-prone and easy to get out of order. ## 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 assessment: Compares delta specs against main specs, optionally runs the inline openspec-sync-specs merge, and verifies the result before archiving. - Use Case: After finishing implementation of a user-auth change, ask the assistant to archive it; the skill confirms artifacts and tasks are done, syncs spec deltas into the main specs, then moves the change into archive/2024-05-01-user-auth/. ## Quick Start Ask the assistant to archive the completed OpenSpec change named add-user-auth and confirm any prompts about incomplete tasks or spec syncing.

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 with a YYYY-MM-DD prefix.

How does OpenSpec sync delta specs before archiving?

The skill compares each delta spec against its main spec and shows a combined summary of adds, modifications, removals, and renames. If you choose to sync, it runs the openspec-sync-specs workflow inline 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 and warns you, but only asks for confirmation rather than blocking. The same applies to artifacts that are neither done nor skipped.

Does the archive workflow work with OpenSpec stores?

Yes. If the work lives in a registered store, the skill runs openspec store list --json to discover store ids and appends --store <id> to all commands that read or write specs and changes for the rest of the workflow.

What happens if the archive target directory already exists?

The archive fails with an error rather than overwriting. The skill suggests renaming the existing archive or using a different date, and it never stacks a second date prefix on an already dated change name.