openspec-archive-change

Archives completed OpenSpec changes after verifying artifact and task completion.

Updated Jun 6, 2026
One-click install
npx skills add https://github.com/jonathanlin768/CS2Match-Nakama --skill openspec-archive-change-jonathanlin768
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/jonathanlin768/CS2Match-Nakama/tree/main/.agents/skills/openspec-archive-change
Command: npx skills add https://github.com/jonathanlin768/CS2Match-Nakama --skill openspec-archive-change-jonathanlin768

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Finalizing a spec-driven change involves checking artifact status, task completion, and delta spec synchronization before moving files into 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 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 feature change, ask the assistant to archive it; the skill warns about incomplete tasks, offers to sync specs, and moves the change into the archive with a summary. ## Quick Start Ask the assistant to archive the completed change named "add-login-flow" using the openspec archive workflow.

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, which checks artifact status with openspec status --json, verifies task completion in tasks.md, then moves the change directory into an archive folder named with the current date and change name.

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

The workflow counts incomplete tasks marked with unchecked boxes and displays a warning with the count. It asks for confirmation before proceeding, so archiving is not blocked but you are informed of remaining work.

Does archiving sync delta specs to main specs automatically?

No, syncing is optional. The workflow compares delta specs against main specs, shows a summary of pending changes, and prompts you to sync now or archive without syncing.

Can I archive a workspace-planning change in OpenSpec?

No. If the status reports actionContext.mode as workspace-planning, the workflow stops and explains that workspace archive is not supported, without moving files or editing linked repos.

What happens if the archive target directory already exists?

The archive fails with an error suggesting you rename the existing archive or use a different date. It never overwrites an existing archived change directory.