skills.rest
twaananen
twaananenCOMMUNITY
Explore all skills by this author →
GitHub

openspec-archive-change

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

Updated Mar 13, 2026
Search Tags:#workflow#cli#archive#change management#openspec#spec sync#task verification
One-click install
npx skills add https://github.com/twaananen/6dof-drone-sim --skill openspec-archive-change-twaananen
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/twaananen/6dof-drone-sim/tree/main/.agents/skills/openspec-archive-change
Command: npx skills add https://github.com/twaananen/6dof-drone-sim --skill openspec-archive-change-twaananen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Finalizing a completed change in an OpenSpec workflow involves checking artifact completion, verifying task status, syncing delta specs, and moving directories, 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 a date-stamped archive folder 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 specs, and archive the change as openspec/changes/archive/YYYY-MM-DD-<name>/. ## Quick Start Archive my completed 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 change in OpenSpec?▼

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, optionally syncs delta specs, then moves the change to `openspec/changes/archive/YYYY-MM-DD-<name>/`.

How to sync delta specs before archiving an OpenSpec change?▼

The workflow compares delta specs in `openspec/changes/<name>/specs/` against main specs and shows a summary of adds, modifications, and removals. You can choose to sync via the openspec-sync-specs skill or archive without syncing.

Can I archive an OpenSpec change with incomplete tasks?▼

Yes, archiving is not blocked by incomplete tasks or artifacts. 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 directory with the same date-stamped name already exists. You are advised to rename the existing archive or use a different date.

Does archiving an OpenSpec change require the openspec CLI?▼

Yes, the openspec CLI is required. The workflow uses `openspec list --json` and `openspec status --change <name> --json` to enumerate changes and check artifact completion status.

Related Skills

Explore More Software Engineering Skills→
MiDouTechMiDouTech

openspec-archive-change

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

Official
Advanced
josemartinrodriguezmortalonijosemartinrodriguezmortaloni

sdd-archive

Sync delta specifications into main specs and archive change folders.

Community
Advanced
QuafadasQuafadas
13

openspec-archive-change

Archive completed OpenSpec changes after validating artifacts, tasks, and delta specs.

Community
Advanced
contenido-wqcontenido-wq

openspec-archive-change

Archive completed openspec changes after validating artifacts and tasks.

Community
Intermediate