openspec-archive-change

Archives completed OpenSpec changes after verifying board status, artifacts, and tasks.

2|Updated Apr 19, 2026
One-click install
npx skills add https://github.com/Wizarck/nexandro --skill openspec-archive-change-wizarck
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/Wizarck/nexandro/tree/main/skills/openspec-archive-change
Command: npx skills add https://github.com/Wizarck/nexandro --skill openspec-archive-change-wizarck

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Finalizing a completed change in an OpenSpec workflow involves several manual checks—verifying the project board status, confirming artifact and task completion, moving directories, and writing a retrospective. This Skill automates that entire archive procedure with built-in guardrails so nothing is archived prematurely. ## Core Features & Use Cases - Board Status Verification: Runs a verification script against the GitHub Project board and refuses to archive unless the item's Status is Done. - Completion Checks: Parses openspec status --json for incomplete artifacts and scans tasks.md for unchecked items, prompting for confirmation before proceeding. - Dated Archive Move: Moves the change directory to openspec/changes/archive/YYYY-MM-DD-<name> with collision detection. - Chained Retrospective: Writes or appends a retrospective stub at retros/<change-id>.md as a mandatory Gate F deliverable. - Use Case: After merging the implementation PR for a change, ask the assistant to archive it; the Skill verifies the board shows Done, confirms all artifacts and tasks are complete, moves the directory, and creates the retro file. ## Quick Start Archive the completed OpenSpec change named add-user-auth after verifying its project board status is Done.

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 prompt you with a selection list from `openspec list --json`. It verifies board status, checks artifacts and tasks, then moves the directory to openspec/changes/archive/YYYY-MM-DD-<name>.

What happens if the GitHub Project board status is not Done?▼

The verify_board_state.py script exits non-zero and the archive is refused. Exit code 1 means status mismatch, 2 means the item was not found, and 3 indicates a GraphQL or network error; the error is surfaced for resolution.

Can I archive a change with incomplete tasks or artifacts?▼

Yes, but only after explicit confirmation. The Skill displays warnings listing incomplete artifacts from `openspec status --json` and counts unchecked tasks in tasks.md, then asks whether to proceed.

Does archiving sync delta specs into the main specs?▼

No. The Skill only performs an informational assessment comparing delta specs against main specs and shows a summary. Automated spec syncing is deferred to a planned spec-sync capability in a future version.

What is the retrospective file created during archiving?▼

Every archive chains a retro write to retros/<change-id>.md as a Gate F deliverable. If a bmad-retrospective skill is available it is invoked; otherwise a structured stub with sections for lessons and carry-forward items is written.