openspec-archive-change

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

Updated Aug 25, 2026
One-click install
npx skills add https://github.com/KevMendesDev/mercadinho-sao-francisco --skill openspec-archive-change-kevmendesdev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/KevMendesDev/mercadinho-sao-francisco/tree/main/.agents/skills/openspec-archive-change
Command: npx skills add https://github.com/KevMendesDev/mercadinho-sao-francisco --skill openspec-archive-change-kevmendesdev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Finalizing a completed change in an OpenSpec workflow involves several error-prone manual steps: checking artifact completion, verifying tasks, syncing delta specs into main specs, and moving the change into an archive directory. This Skill automates that entire finalization flow with 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. - Completion verification: Checks artifact status via openspec status --json and counts incomplete tasks in tasks.md, warning before proceeding. - 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 dated archive/ folder, failing if the target already exists. - 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 archive/2025-01-15-user-auth. ## Quick Start Ask the agent to archive the completed change named add-user-auth using the openspec archive workflow.

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?▼

Run 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 a dated archive folder.

How does OpenSpec sync delta specs before archiving?▼

The Skill compares each delta spec against its main spec, shows a combined summary, and prompts to sync. If confirmed, it runs the openspec-sync-specs workflow inline and re-verifies every capability before archiving.

Can I archive a change with incomplete tasks in OpenSpec?▼

Yes. The Skill counts incomplete tasks marked with unchecked boxes and displays a warning, but only asks for confirmation before proceeding. Archiving is not blocked by incomplete tasks or artifacts.

What happens if the archive target directory already exists?▼

The archive fails with an error suggesting you rename the existing archive or use a different date. Target names use a YYYY-MM-DD prefix, and a second date is never stacked onto an already-prefixed name.

Does the archive workflow support multiple OpenSpec stores?▼

Yes. If the user names a store, the Skill runs openspec store list to discover registered store ids and passes the store flag on all commands that read or write specs and changes for the rest of the workflow.