openspec-archive-change

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

1|Updated Jul 14, 2026
One-click install
npx skills add https://github.com/pablof7z/pod0 --skill openspec-archive-change-pablof7z
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/pablof7z/pod0/tree/main/.agents/skills/openspec-archive-change
Command: npx skills add https://github.com/pablof7z/pod0 --skill openspec-archive-change-pablof7z

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 through the openspec CLI. ## Core Features & Use Cases - Completion Verification: Checks artifact status via openspec status --json and counts incomplete tasks in tasks.md before archiving, warning and confirming with the user when anything is unfinished. - Delta Spec Sync Assessment: Compares delta specs against main specs, summarizes pending adds, modifications, removals, and renames, and optionally runs an inline sync workflow with verification before archiving. - Dated Archiving: Moves the change directory into an archive folder with a YYYY-MM-DD- prefixed name, failing safely 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 into the dated archive with a summary report. ## 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?▼

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

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

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

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

Yes, archiving is not blocked by incomplete artifacts or tasks. The Skill displays a warning listing incomplete items and asks for confirmation before proceeding, then notes the warnings in the final summary.

Does openspec archive work with named 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.

What happens if the archive target directory already exists?▼

The archive fails with an error rather than overwriting anything. The Skill suggests renaming the existing archive or using a different date, and the change directory remains untouched.