openspec-archive-change

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

1|1|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/creevey/rprtr --skill openspec-archive-change-creevey
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/creevey/rprtr/tree/main/.opencode/skills/openspec-archive-change
Command: npx skills add https://github.com/creevey/rprtr --skill openspec-archive-change-creevey

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Finalizing a completed change in an OpenSpec workflow involves several error-prone manual steps: checking artifact completion, verifying tasks, syncing delta specs into main specs, and moving the change directory into a dated archive. This Skill automates that entire finalization sequence with built-in verification and confirmation prompts. ## Core Features & Use Cases - Completion Verification: Checks artifact status via openspec status --json and counts incomplete tasks in tasks.md, warning before archiving unfinished work. - Delta Spec Sync Assessment: Compares delta specs against main specs, summarizes pending adds, modifications, removals, and renames, and optionally runs an inline sync before archiving. - Dated Archive Move: Moves the change directory into an archive/ folder with a YYYY-MM-DD- prefixed name, failing safely if the target already exists. - Use Case: After implementing a feature tracked as an OpenSpec change, ask the assistant to archive it; the Skill verifies all artifacts and tasks, syncs specs if needed, and moves the change into the archive with a summary report. ## Quick Start Ask the assistant to archive the completed OpenSpec change, optionally naming the change to 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 OpenSpec change?

Run the archive workflow with the change name, or let it be inferred from context. The Skill 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 I archive a change with incomplete tasks?

The Skill counts incomplete tasks marked with `- [ ]` in the tasks file and displays a warning with the count. It asks for confirmation before proceeding, so archiving with incomplete tasks is allowed but never silent.

Does archiving sync delta specs into the main specs?

Yes, when delta specs exist the Skill compares them against main specs and offers to sync before archiving. The sync runs inline and is verified against every capability; if verification fails, the archive stops without moving anything.

Can I archive a change in a named OpenSpec store?

Yes. Run `openspec store list --json` to discover registered store ids, then pass `--store <id>` on the 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 suggesting you rename the existing archive or use a different date. The change directory is never overwritten or partially moved, so nothing is lost.