openspec-archive-change

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

Updated Jun 28, 2026
One-click install
npx skills add https://github.com/hongwt/dsplm-monitor --skill openspec-archive-change-hongwt
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/hongwt/dsplm-monitor/tree/main/.pi/skills/openspec-archive-change
Command: npx skills add https://github.com/hongwt/dsplm-monitor --skill openspec-archive-change-hongwt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Finalizing a completed change in an OpenSpec workflow involves several manual checks—artifact completion, task status, delta spec synchronization, and moving files into a dated archive—which are easy to skip or perform inconsistently. ## Core Features & Use Cases - Guided Change Selection: Resolves the target change from user input, conversation context, or an interactive prompt listing active changes. - Completion Verification: Checks artifact status via openspec status --json and counts incomplete tasks in tasks.md before archiving, warning but not blocking on gaps. - Delta Spec Sync Assessment: Compares delta specs against main specs, optionally runs an inline sync workflow, and verifies the result before moving anything. - Dated Archiving: Moves the change directory into an archive folder with a YYYY-MM-DD- prefix, preventing duplicate targets. - Use Case: After finishing implementation of a user-auth change, ask the assistant to archive it; it confirms all artifacts are done, syncs the delta specs into the main specs, and moves the change to the archive with a dated name. ## Quick Start Archive the completed change named add-user-auth and sync its delta specs into the main 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 change in OpenSpec?▼

Provide the change name or let the workflow infer it from context. It checks artifact and task completion, assesses delta spec sync state, then moves the change directory into an archive folder with a YYYY-MM-DD- prefix.

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

The workflow counts tasks marked with `- [ ]` in tasks.md and displays a warning with the incomplete count. It asks for confirmation but does not block the archive if you choose to proceed.

Does archiving sync delta specs to the main specs?▼

Yes, if delta specs exist you are prompted to sync before archiving. The sync runs inline as an agent-driven merge, then the result is re-verified against every capability before the change directory is moved.

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

Yes. Run `openspec store list --json` to discover registered store ids, then pass `--store <id>` on all commands that read or write specs and changes. The flag stays sticky for the rest of the workflow.

What happens if the archive target directory already exists?▼

The archive fails with an error rather than overwriting. You are advised to rename the existing archive or use a different date prefix before retrying.