skills.rest
yujikawa
yujikawaCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

openspec-archive-change

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

Updated Feb 25, 2026
Search Tags:#workflow#cli#archive#change management#spec-driven development#openspec#spec sync
One-click install
npx skills add https://github.com/yujikawa/modscape --skill openspec-archive-change-yujikawa
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/yujikawa/modscape/tree/main/.gemini/skills/openspec-archive-change
Command: npx skills add https://github.com/yujikawa/modscape --skill openspec-archive-change-yujikawa

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, 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 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 offers to sync before archiving. - Safe Archiving: Moves the change 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, optionally syncs specs, and archives the change with a dated folder name. ## Quick Start Archive the completed change "add-user-auth" after verifying its artifacts and tasks are done.

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?▼

Invoke the archive workflow with an optional change name; if omitted, it lists active changes via openspec list --json and prompts you to select one. It then verifies completion and moves the change to openspec/changes/archive/YYYY-MM-DD-<name>.

What happens if artifacts or tasks are incomplete when archiving?▼

The skill displays a warning listing incomplete artifacts from openspec status --json and counts unchecked tasks in tasks.md. It asks for confirmation before proceeding, so archiving is never blocked but always informed.

Does archiving sync delta specs to the main specs?▼

If delta specs exist under openspec/changes/<name>/specs/, the skill compares them with main specs and shows a summary. You can choose to sync via the openspec-sync-specs skill or archive without syncing.

What if the archive target directory already exists?▼

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

What are the requirements to use the OpenSpec archive workflow?▼

You need the openspec CLI installed and a project with an openspec/changes directory structure. The skill relies on openspec list and openspec status commands for change discovery and completion checks.

Related Skills

Explore More Software Engineering Skills→
carlosapgomescarlosapgomes

openspec-archive-change

Archive completed OpenSpec changes after validating artifacts and tasks.

Community
Advanced
ssd-mkdocs-platformssd-mkdocs-platform
1

openspec-archive-change

Archive completed OpenSpec changes under openspec/changes/archive with metadata.

Official
Advanced
mazhewittmazhewitt

openspec-sync-specs

Merge delta specification changes into canonical main specs with idempotent updates.

Community
Advanced
MiDouTechMiDouTech

openspec-archive-change

Archive completed openspec changes into date-prefixed directories after verification.

Official
Advanced