openspec-archive-change

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

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

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 task lists, syncing delta specs into main specs, and moving the change directory into a dated archive. This Skill automates that entire finalization sequence through the openspec CLI. ## Core Features & Use Cases - Guided change selection: Infers the change from conversation context, auto-selects when only one active change exists, or prompts with a list of active changes when ambiguous. - Completion and sync verification: Checks artifact status via openspec status --json, counts incomplete tasks in tasks.md, and compares delta specs against main specs before archiving, optionally running an inline spec sync with verification. - Safe dated archiving: Creates the archive directory, generates a YYYY-MM-DD-<change-name> target without double-dating, fails on name collisions, and moves the change root while preserving .openspec.yaml. - Use Case: After finishing implementation of a user-auth change, ask the assistant to archive it; the Skill verifies all artifacts and tasks, syncs the delta specs into the main specs, and moves the change into the dated archive folder. ## Quick Start Ask the assistant to archive the completed OpenSpec change named add-user-auth and confirm any warnings about incomplete tasks or unsynced specs.

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 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 tasks are incomplete when archiving a change?▼

The Skill counts incomplete tasks marked with `- [ ]` in tasks.md and displays a warning with the count. It asks for confirmation before proceeding, so archiving is never blocked but you are informed of unfinished work.

Does the archive workflow sync delta specs into main specs?▼

Yes. If delta specs exist, it compares them against main specs, shows a summary, and offers to sync before archiving. After syncing, it re-verifies every capability and stops without archiving if any mismatch remains.

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

Yes. Run openspec store list --json to discover registered store ids, then pass --store <id> on 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 not moved, so nothing is lost and you can retry after resolving the collision.