skills.rest
33may
33mayCOMMUNITY
Explore all skills by this author →
GitHub

openspec-archive-change

Archives completed OpenSpec changes after verifying artifact and task completion status.

1|1|Updated Nov 28, 2025
Search Tags:#workflow#cli#archive#change management#spec-driven development#openspec#task verification
One-click install
npx skills add https://github.com/33may/robotics --skill openspec-archive-change-33may
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/33may/robotics/tree/main/humanoid/.claude/skills/openspec-archive-change
Command: npx skills add https://github.com/33may/robotics --skill openspec-archive-change-33may

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Finalizing a completed change in an OpenSpec workflow involves checking artifact status, task completion, and spec synchronization before moving files to an archive, which is error-prone when done manually. ## Core Features & Use Cases - Completion Verification: Checks artifact status via openspec status --json and counts incomplete tasks in tasks.md before archiving. - 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 into a date-prefixed archive folder (YYYY-MM-DD-name) with collision detection. - Use Case: After finishing implementation of a feature change, ask the assistant to archive it; the skill prompts you to select the change, warns about incomplete tasks, syncs specs if needed, and moves the change into the archive. ## Quick Start Ask the assistant to archive the completed change named add-user-auth using the openspec archive workflow.

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 and optionally provide a change name. If omitted, the skill runs openspec list --json and prompts you to select from active changes, then verifies completion and moves the change to a date-prefixed archive directory.

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

The skill counts incomplete tasks marked with unchecked boxes in tasks.md and displays a warning with the count. It asks for confirmation before proceeding, so archiving is not blocked but you are informed.

Does the archive process sync delta specs to main specs?▼

Yes, if delta specs exist, the skill compares them against main specs under openspec/specs and shows a summary of changes. You can choose to sync via the openspec-sync-specs skill or archive without syncing.

Can I archive workspace-planning changes with this skill?▼

No. If the status JSON reports actionContext.mode as workspace-planning, the skill stops and explains that workspace archive is not supported. It does not move workspace changes into repo-local archives.

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 target name follows the format YYYY-MM-DD-change-name under the changes archive directory.

Related Skills

Explore More Software Engineering Skills→
carlosapgomescarlosapgomes

openspec-archive-change

Archive completed OpenSpec changes after validating artifacts and tasks.

Community
Advanced
sandgardenhqsandgardenhq
130

tracing-knowledge-lineages

Trace technical decision origins using Git history and decision records.

Official
Intermediate
CoderCoco-StudiosCoderCoco-Studios
1

openspec-archive-change

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

Official
Advanced
MiDouTechMiDouTech

openspec-archive-change

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

Official
Advanced