openspec-archive-change

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

4|Updated Jun 21, 2026
One-click install
npx skills add https://github.com/NEETROF/cymbra --skill openspec-archive-change-neetrof
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/NEETROF/cymbra/tree/main/.cursor/skills/openspec-archive-change
Command: npx skills add https://github.com/NEETROF/cymbra --skill openspec-archive-change-neetrof

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, and moving directories—which is error-prone when done by hand. ## 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 archiving: Moves the change directory into an archive/ folder named YYYY-MM-DD-<change-name> with collision detection. - Use Case: After finishing implementation of a feature change, ask the assistant to archive it; the skill verifies everything is complete, syncs specs if needed, and files the change away with a dated archive entry. ## Quick Start Archive the completed change "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 change in OpenSpec?▼

Run 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, then moves the change directory into an archive folder named with the current date.

What happens if tasks are incomplete when archiving a change?▼

The skill counts incomplete tasks marked with `- [ ]` in the tasks file and displays a warning with the count. It asks for confirmation before proceeding, so archiving is never blocked but you stay informed.

Does archiving sync delta specs to the main specs?▼

Yes, if delta specs exist the skill compares them against the main specs and shows a summary of adds, modifications, and removals. You can choose to sync before archiving or archive without syncing.

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. Workspace-planning mode changes are not supported and will stop the archive process.

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

The archive fails with an error rather than overwriting. You are advised to rename the existing archive or use a different date before retrying.