openspec-archive-change

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

1|Updated Oct 27, 2025
One-click install
npx skills add https://github.com/WndDnz/modelo-relatorio-unifei-ict --skill openspec-archive-change-wnddnz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/WndDnz/modelo-relatorio-unifei-ict/tree/main/.opencode/skills/openspec-archive-change
Command: npx skills add https://github.com/WndDnz/modelo-relatorio-unifei-ict --skill openspec-archive-change-wnddnz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Finalizing a completed change in an OpenSpec workflow involves several error-prone manual checks: confirming artifacts are done, verifying tasks are complete, 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 guardrails. ## 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 Synchronization: Compares delta specs against main specs, optionally runs an inline sync workflow, and re-verifies every capability before archiving. - Dated Archiving: Moves the change directory into an archive/ folder with a YYYY-MM-DD- prefixed name, preventing duplicate-date collisions. - Use Case: After finishing implementation of a user-auth change, ask the assistant to archive it; the Skill confirms all artifacts and tasks are done, syncs spec changes into the main specs, and moves the change into the archive with a summary report. ## Quick Start Archive the completed OpenSpec change named add-user-auth, syncing its delta specs into the main specs first.

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?

Invoke the archive workflow with the change name, or let it infer the change from context. The Skill checks artifact and task completion, optionally syncs delta specs, then moves the change directory into an archive folder with a date-prefixed name.

How to sync delta specs into main specs before archiving?

The Skill compares each delta spec against its main spec and prompts you to sync. If confirmed, it runs the openspec-sync-specs workflow inline, then re-verifies every capability to confirm additions, modifications, removals, and renames were applied.

Can I archive an OpenSpec change with incomplete tasks?

Yes, but the Skill warns you first. It counts incomplete tasks marked with unchecked boxes and lists unfinished artifacts, then asks for confirmation before proceeding with the archive.

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 throughout the workflow.

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, and never stacks a second date prefix on an already dated change name.