skills.rest
JaimeHoracio
JaimeHoracioCOMMUNITY
Explore all skills by this author →
GitHub

openspec-archive-change

Archives completed OpenSpec changes after verifying artifact and task completion.

1|Updated Jun 6, 2026
Search Tags:#workflow#cli#archive#change management#spec-driven development#openspec
One-click install
npx skills add https://github.com/JaimeHoracio/Ostacky --skill openspec-archive-change-jaimehoracio
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/JaimeHoracio/Ostacky/tree/main/assets/skills/openspec-archive-change
Command: npx skills add https://github.com/JaimeHoracio/Ostacky --skill openspec-archive-change-jaimehoracio

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Finalizing a spec-driven change 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, sync delta specs into the main specs, and archive the change with a dated folder name. ## Quick Start Archive the completed change "add-user-auth" and sync its delta specs before moving it to the archive.

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 list active changes via `openspec list --json` so you can pick one. It verifies artifacts and tasks, then moves the directory to openspec/changes/archive/YYYY-MM-DD-<name>.

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

The workflow counts tasks marked `- [ ]` in tasks.md and warns you with the incomplete count. It asks for confirmation before proceeding, so archiving is never blocked but always informed.

Does archiving sync delta specs to the main specs?▼

Yes, if delta specs exist under openspec/changes/<name>/specs/, the workflow compares them with main specs and shows a summary. You can choose to sync before archiving or archive without syncing.

What 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.

What are the requirements for using the OpenSpec archive workflow?▼

You need the openspec CLI installed and a project with an openspec/changes directory containing the change to archive. The change should have artifacts tracked by `openspec status` and optionally a tasks.md file.

Related Skills

Explore More Software Engineering Skills→
zabinyzabiny
2

openspec-archive-change

Archive completed OpenSpec changes after validating artifacts, tasks, and delta-spec status.

Official
Advanced
UnterrainerInformatikUnterrainerInformatik

openspec-sync-specs

Sync delta specs from an OpenSpec change into main specification files.

Official
Intermediate
Pony-UnicornPony-Unicorn
7

openspec-archive-change

Archive completed openspec changes after verifying artifact and task status.

Community
Advanced
AlmogMaayanAlmogMaayan

openspec-archive-change

Archives completed OpenSpec changes and syncs delta specs into main specifications.

Community
Intermediate