skills.rest
Joao-Camilo-Mallmann
Joao-Camilo-MallmannCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

openspec-archive-change

Archive completed OpenSpec changes after verifying artifact and task completion.

Updated Aug 29, 2026
Search Tags:#workflow#cli#tasks#archive#change management#spec-driven development#openspec
One-click install
npx skills add https://github.com/Joao-Camilo-Mallmann/ofurry-motion-graphics --skill openspec-archive-change-joao-camilo-mallmann
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/Joao-Camilo-Mallmann/ofurry-motion-graphics/tree/main/.agents/skills/openspec-archive-change
Command: npx skills add https://github.com/Joao-Camilo-Mallmann/ofurry-motion-graphics --skill openspec-archive-change-joao-camilo-mallmann

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Finalizing a completed change in an OpenSpec workflow involves checking artifact status, task completion, and delta spec synchronization before moving files, 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 a sync before archiving. - Safe Archiving: Moves the change directory into a date-stamped archive folder (YYYY-MM-DD-name) with collision detection. - Use Case: After finishing implementation of a spec-driven change, ask the assistant to archive it; the skill verifies everything is done, warns about incomplete items, and archives the change with a clear summary. ## Quick Start Archive the completed change named add-user-auth and confirm any warnings about incomplete artifacts.

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 the change name, or let the skill list active changes for selection. It verifies artifact and task completion, assesses delta spec sync state, then moves the change directory into an archive folder named with the current date.

What happens if tasks are incomplete when archiving an OpenSpec change?▼

The skill counts incomplete tasks marked with '- [ ]' in tasks.md and displays a warning with the count. It asks for confirmation before proceeding, so archiving is never blocked but you are informed of unfinished work.

Does openspec archive sync delta specs automatically?▼

No, it assesses delta specs against main specs and shows a summary of pending changes first. You can choose to sync via the openspec-sync-specs skill, archive without syncing, or cancel.

Can I archive a change in a specific OpenSpec store?▼

Yes, if you name a store, the skill runs 'openspec store list --json' to discover registered store ids and passes '--store <id>' to commands that read or write specs and changes. Without a store, commands act on the nearest local openspec root.

What happens if the archive target directory already exists?▼

The archive fails with an error rather than overwriting. The skill suggests renaming the existing archive or using a different date, since target names follow the YYYY-MM-DD-change-name format.

Related Skills

Explore More Software Engineering Skills→
formioformio
6

openspec-archive-change

Archive completed changes in an openspec experimental workflow.

Official
Intermediate
Alan-TheGentlemanAlan-TheGentleman
10

sdd-archive

Merge delta specs into main specs and archive completed changes.

Community
Advanced
cynkracynkra
1

openspec-sync-specs

Merge delta OpenSpec requirement blocks into main spec files per capability.

Official
Intermediate
MiDouTechMiDouTech

openspec-archive-change

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

Official
Advanced