openspec-archive-change

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

Updated Jul 31, 2026
One-click install
npx skills add https://github.com/germainlefebvre4/cvwonder-forms --skill openspec-archive-change-germainlefebvre4
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/germainlefebvre4/cvwonder-forms/tree/main/.gemini/skills/openspec-archive-change
Command: npx skills add https://github.com/germainlefebvre4/cvwonder-forms --skill openspec-archive-change-germainlefebvre4

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Finalizing a completed change in an OpenSpec workflow involves several manual checks: confirming artifacts are done, verifying tasks are complete, syncing delta specs into main specs, and moving the change directory into an archive. This Skill automates that entire finalization sequence through the openspec CLI. ## Core Features & Use Cases - Change Selection & Validation: Resolves the target change from user input or conversation context, and checks artifact and task completion status via openspec status --json. - Delta Spec Synchronization: Compares delta specs against main specs, optionally runs an inline sync workflow, and verifies the merge before archiving. - Safe Archiving: Moves the change directory into a date-prefixed archive folder with collision detection and a clear completion summary. - Use Case: After finishing implementation of a feature change, ask the assistant to archive it; the Skill checks for incomplete tasks, syncs spec updates, and moves the change into the archive with a full report. ## Quick Start Archive the completed change 'add-user-auth' and sync its delta specs into the main specs.

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 via openspec status, optionally syncs delta specs, then moves the change directory into a date-prefixed archive folder.

How to sync delta specs to main specs before archiving?

The Skill compares each delta spec against its main spec and prompts you to sync. If confirmed, it runs the openspec-sync-specs workflow inline, then 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 warns you, but archiving proceeds after your confirmation. The summary notes how many tasks were incomplete.

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. The change directory is not moved, so nothing is lost and you can retry.

Does openspec archive require the openspec CLI installed?

Yes. The Skill requires the openspec CLI and uses commands like openspec status, list, and instructions with JSON output. It also supports multi-store setups via the --store flag.