openspec-archive-change

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

Updated Jun 24, 2026
One-click install
npx skills add https://github.com/aguachis/Nicole-DB --skill openspec-archive-change-aguachis
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/aguachis/Nicole-DB/tree/main/.agents/skills/openspec-archive-change
Command: npx skills add https://github.com/aguachis/Nicole-DB --skill openspec-archive-change-aguachis

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 the archive with a correct date prefix. This Skill automates that entire finalization sequence through the openspec CLI. ## 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 assessment: Compares delta specs against main specs, optionally runs the inline sync workflow, and verifies the result before archiving. - Safe archiving: Creates the archive directory, applies a YYYY-MM-DD- date prefix without double-stacking, and refuses to overwrite an existing archive target. - Use Case: After finishing implementation of a feature change, ask the agent to archive it; the Skill verifies everything is done, syncs specs if needed, moves the change into changes/archive/, and prints a summary. ## Quick Start Archive the completed change named add-user-auth and sync its delta specs into the main specs before moving it.

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. It checks artifact and task completion, assesses delta spec sync state, then moves the change directory into the archive folder with a YYYY-MM-DD date prefix.

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

When delta specs exist, the workflow 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 move proceeds.

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

Yes, but only after confirmation. The workflow warns you about incomplete artifacts or unchecked tasks and asks whether to proceed; it never blocks archiving on warnings alone, and the summary notes what was incomplete.

Does openspec archive work with registered stores?▼

Yes. If the work lives in a registered store, run openspec store list --json to find the store id, then pass --store <id> on all spec and change commands. The flag stays sticky for the rest of the workflow.

What happens if the archive target directory already exists?▼

The archive fails with an error rather than overwriting anything. You are advised to rename the existing archive entry or use a different date prefix, and the change directory remains untouched.