skills.rest
TranVanTienDat
TranVanTienDatCOMMUNITY
Explore all skills by this author →
GitHub

openspec-archive-change

Archive completed OpenSpec changes after verifying artifact and task completion.

Updated Mar 26, 2026
Search Tags:#archive#change management#spec-driven development#openspec#delta specs#cli workflow
One-click install
npx skills add https://github.com/TranVanTienDat/Milkyway --skill openspec-archive-change-tranvantiendat
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/TranVanTienDat/Milkyway/tree/main/agent-core/.cursor/skills/openspec-archive-change
Command: npx skills add https://github.com/TranVanTienDat/Milkyway --skill openspec-archive-change-tranvantiendat

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 offers to sync changes 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, run this Skill to confirm all artifacts and tasks are done, optionally sync delta specs to the main specs, and archive the change with a dated folder name. ## Quick Start Archive my completed OpenSpec change and sync its delta specs to the main specs first.

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

Run the archive workflow with a change name, or let it prompt you to select from active changes via `openspec list --json`. 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 workflow compares delta specs in openspec/changes/<name>/specs/ against main specs and shows a summary of additions, modifications, and removals. You can choose to sync via the openspec-sync-specs skill before archiving.

Can I archive a change with incomplete tasks or artifacts?▼

Yes, archiving is not blocked by incomplete artifacts or tasks. The workflow displays a warning listing incomplete items and asks for confirmation before proceeding.

What happens if the archive target directory already exists?▼

The archive fails with an error if a folder with the same date-based name already exists. You are advised to rename the existing archive or use a different date.

Does archiving require the openspec CLI?▼

Yes, the openspec CLI is required. It is used to list available changes and check artifact completion status through JSON output before the archive move is performed.

Related Skills

Explore More Software Engineering Skills→
MiDouTechMiDouTech

openspec-archive-change

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

Official
Advanced
ValyntValynt

openspec-archive-change

Archive completed changes with artifact checks and optional delta-spec sync.

Official
Advanced
agoodwayagoodway

openspec-archive-change

Archive completed openspec workflow changes into dated directories after validating completion.

Official
Advanced
Gentleman-ProgrammingGentleman-Programming
1.3k

sdd-archive

Merge delta specs into main specs and archive completed changes.

Official
Advanced