openspec-archive-change

Archives completed OpenSpec changes with artifact, task, and spec sync verification.

Updated Apr 6, 2026
One-click install
npx skills add https://github.com/capella-hotel-group/capella-hotel-group-poc --skill openspec-archive-change-capella-hotel-group
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/capella-hotel-group/capella-hotel-group-poc/tree/main/.github/skills/openspec-archive-change
Command: npx skills add https://github.com/capella-hotel-group/capella-hotel-group-poc --skill openspec-archive-change-capella-hotel-group

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Finalizing a completed change in an OpenSpec-driven workflow involves several manual checks—verifying artifact completion, confirming tasks are done, syncing delta specs into main specs, and moving the change directory into a dated archive. This Skill automates that entire finalization sequence so nothing is archived prematurely or left out of sync. ## Core Features & Use Cases - Guided change selection: Lists active changes via openspec list --json and prompts the user to pick one instead of guessing. - Completion verification: Checks artifact status with openspec status --json and counts incomplete tasks in tasks.md, warning before proceeding. - Delta spec sync assessment: Compares delta specs against main specs and optionally triggers a sync before archiving. - Dated archival: Moves the change into openspec/changes/archive/YYYY-MM-DD-<name> with collision detection. - Use Case: After finishing implementation of a feature change, ask the assistant to archive it; the Skill verifies all artifacts and tasks, offers to sync specs, and produces a dated archive entry with a summary report. ## Quick Start Archive the completed change named add-user-auth and sync its delta specs before moving it to the archive.

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 a change name, or let it list active changes via openspec list --json so you can select one. It verifies artifacts and tasks, optionally syncs delta specs, then moves the change to openspec/changes/archive/YYYY-MM-DD-<name>.

What happens if I archive a change with incomplete tasks?▼

The workflow counts incomplete tasks marked with - [ ] in tasks.md and displays a warning with the count. You are asked to confirm before proceeding, so archiving is never blocked but always informed.

Does archiving sync delta specs to the main specs?▼

Yes, if delta specs exist under openspec/changes/<name>/specs/, the workflow compares them with main specs and shows a summary. You can choose to sync before archiving or archive without syncing.

What if an archive with the same date and name already exists?▼

The archive step fails with an error when the target directory openspec/changes/archive/YYYY-MM-DD-<name> already exists. It suggests renaming the existing archive or using a different date.

What are the requirements for using the OpenSpec archive workflow?▼

You need the openspec CLI installed, since the workflow runs openspec list and openspec status commands. The change must live under openspec/changes/ in a repository using the OpenSpec experimental workflow.