openspec-archive-change

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

Updated Jan 5, 2025
One-click install
npx skills add https://github.com/ValorVie/settingZsh --skill openspec-archive-change-valorvie
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/ValorVie/settingZsh/tree/main/.gemini/skills/openspec-archive-change
Command: npx skills add https://github.com/ValorVie/settingZsh --skill openspec-archive-change-valorvie

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Finalizing a completed change in an OpenSpec workflow involves several manual checks—verifying artifact completion, confirming tasks are done, syncing delta specs to main 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, never auto-selecting. - 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 the openspec-sync-specs workflow before archiving. - Safe Archiving: Moves the change directory to 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 everything is complete, syncs specs if needed, and archives with a dated folder name. ## Quick Start Ask the assistant to archive the completed OpenSpec change named "add-user-auth" and confirm any warnings about incomplete artifacts or tasks.

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 skill 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 directory to openspec/changes/archive/YYYY-MM-DD-<name>.

How to sync delta specs before archiving a change?▼

The skill compares delta specs under openspec/changes/<name>/specs/ with main specs and shows a summary of additions, modifications, and removals. If you choose to sync, it delegates to the openspec-sync-specs skill before archiving.

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

The skill counts incomplete tasks marked with - [ ] in tasks.md and displays a warning with the count. It asks for confirmation before proceeding, so archiving is never blocked—only confirmed.

Does archiving a change require the openspec CLI?▼

Yes, the skill requires the openspec CLI to run openspec list --json and openspec status --json for change discovery and artifact completion checks. Directory moves use standard shell commands.

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

The archive fails with an error if the target openspec/changes/archive/YYYY-MM-DD-<name> already exists. You are advised to rename the existing archive or use a different date before retrying.