skills.rest
QlikL
QlikLCOMMUNITY
Explore all skills by this author →
GitHub

openspec-archive-change

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

1|Updated Jun 22, 2026
Search Tags:#archive#change management#spec-driven development#openspec#task verification#cli workflow
One-click install
npx skills add https://github.com/QlikL/pet-shop --skill openspec-archive-change-qlikl
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/QlikL/pet-shop/tree/main/.trae/skills/openspec-archive-change
Command: npx skills add https://github.com/QlikL/pet-shop --skill openspec-archive-change-qlikl

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Finalizing a completed change in an OpenSpec-driven workflow involves several manual checks—verifying artifacts, counting unfinished tasks, syncing delta specs, and moving directories—which are easy to skip or perform inconsistently. ## Core Features & Use Cases - Completion Verification: Checks artifact status via openspec status --json and counts incomplete tasks in tasks.md, warning the user before archiving unfinished work. - Delta Spec Sync Assessment: Compares delta specs against main specs and offers to sync changes before archiving. - Safe Archiving: Moves the change directory into openspec/changes/archive/ with a date-prefixed name, failing safely if the target already exists. - Use Case: After finishing implementation of a feature change, ask the assistant to archive it; the skill prompts you to pick the change, warns about any incomplete tasks, optionally syncs specs, and archives the change with a dated folder name. ## Quick Start Archive the completed OpenSpec change for the feature I just finished implementing.

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 lists active changes via openspec list and prompts you to select one. It then verifies completion and moves the directory to openspec/changes/archive with a date prefix.

What happens if I archive a change with incomplete tasks?▼

The skill counts tasks marked with '- [ ]' in tasks.md and displays a warning showing how many are incomplete. It asks for confirmation before proceeding, so archiving is never blocked but you are always informed.

Does archiving sync delta specs to the main specs?▼

If delta specs exist under the change's specs directory, the skill compares them with the main specs and shows a summary of pending changes. You can choose to sync before archiving or archive without syncing.

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

The openspec CLI must be installed and the project must contain an openspec/changes directory with active changes. The skill relies on openspec list and openspec status commands returning JSON output.

Why does archiving fail with a target already exists error?▼

The archive target name is generated as YYYY-MM-DD-<change-name>, so archiving the same change twice on one day collides. Rename the existing archive folder or wait for a different date to resolve the conflict.

Related Skills

Explore More Software Engineering Skills→
MiDouTechMiDouTech

openspec-archive-change

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

Official
Advanced
amauryconstantamauryconstant
6

osx-generate-changelog

Generate a CHANGELOG.md from archived OpenSpec changes using Keep a Changelog format.

Community
Intermediate
emergent-companyemergent-company
1

openspec-bulk-archive-change

Archive multiple completed changes with openspec CLI after validating status and resolving conflicts.

Official
Advanced
memorysavermemorysaver

openspec-onboard

Guide users through the OpenSpec change lifecycle with in-repo tasks.

Community
Advanced