skills.rest
RuixeWolf
RuixeWolfCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

openspec-archive-change

Archive completed OpenSpec changes after verifying artifacts, tasks, and spec synchronization.

4|Updated May 13, 2026
Search Tags:#workflow automation#cli#archive#change management#spec-driven development#openspec
One-click install
npx skills add https://github.com/RuixeWolf/modbus-simulator --skill openspec-archive-change-ruixewolf
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/RuixeWolf/modbus-simulator/tree/main/.opencode/skills/openspec-archive-change
Command: npx skills add https://github.com/RuixeWolf/modbus-simulator --skill openspec-archive-change-ruixewolf

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Finalizing a completed change in an OpenSpec workflow involves multiple manual checks—artifact completion, task status, and delta spec synchronization—before safely moving the change into the archive. This Skill automates that entire finalization sequence with the openspec CLI. ## Core Features & Use Cases - Guided Change Selection: Resolves the target change from user input, conversation context, or an interactive prompt listing active changes. - Pre-Archive Verification: Checks artifact completion via openspec status --json, counts incomplete tasks in tasks.md, and warns before proceeding. - Delta Spec Sync Assessment: Compares delta specs against main specs, optionally runs an inline sync workflow, and verifies the result before archiving. - Use Case: After finishing implementation of a feature change, ask the assistant to archive it; the Skill validates everything, syncs specs if needed, and moves the change into a date-prefixed archive directory. ## Quick Start Archive the completed change 'add-user-auth' and sync its delta specs to the main specs before archiving.

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

Invoke the archive workflow with a change name, or let it infer the change from context. The Skill checks artifact and task completion, assesses delta spec sync state, then moves the change into a date-prefixed archive directory.

How to sync delta specs to main specs before archiving?▼

The Skill compares each delta spec against its main spec and prompts you to sync. If you confirm, it runs the openspec-sync-specs workflow inline, then re-verifies every capability before archiving.

Does openspec archive work with registered stores?▼

Yes. If the work lives in a registered store, the Skill discovers store ids with openspec store list --json and passes --store <id> on all commands that read or write specs and changes.

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

The Skill counts incomplete tasks marked with '- [ ]' and displays a warning with the count. It asks for confirmation and proceeds with the archive if you approve, noting the warning in the summary.

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

The archive target name is the change name prefixed with the current date. If a directory with that name already exists in the archive folder, the Skill fails and suggests renaming the existing archive or using a different date.

Related Skills

Explore More Software Engineering Skills→
carlosapgomescarlosapgomes

openspec-archive-change

Archive completed OpenSpec changes after validating artifacts and tasks.

Community
Advanced
Gentleman-ProgrammingGentleman-Programming
1.3k

sdd-archive

Merge delta specs into main specs and archive completed changes.

Official
Advanced
izzoaizzoa
22

openspec-archive-change

Archive completed OpenSpec changes after validating artifact and task status.

Community
Advanced
ESO-ToolkitESO-Toolkit
2

rebase

Automate rebasing stacked Git branches after a squash merge.

Official
Advanced