openspec-archive-change

Archives completed openspec change requests with spec sync, ADR extraction, and knowledge capture.

Updated Jun 26, 2026
One-click install
npx skills add https://github.com/pavelvdo/universal-xml-exchange2 --skill openspec-archive-change-pavelvdo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/pavelvdo/universal-xml-exchange2/tree/main/.cursor/skills/openspec-archive-change
Command: npx skills add https://github.com/pavelvdo/universal-xml-exchange2 --skill openspec-archive-change-pavelvdo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Finalizing a completed change request involves many error-prone manual steps: verifying tasks, syncing delta specs, extracting architecture decisions, and moving files to an archive. This Skill automates that entire closeout workflow so nothing is forgotten. ## Core Features & Use Cases - Automated closeout gates: Verifies artifact completion, developer comment marker balance, slice acceptance status, and code-truth consistency before archiving, blocking the archive on hard failures. - Spec and knowledge sync: Automatically merges delta specs into main specs, extracts ADR-worthy decisions from architecture reports, and saves reusable knowledge-base facts. - Use Case: After finishing a 1C development change tracked in openspec, run the archive command to verify all slices are accepted, sync the spec deltas, record ADRs, and move the change folder into the dated archive directory in one step. ## Quick Start Archive the completed change by asking the assistant to run the archive workflow for the current openspec change.

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 command with the change name, or let the assistant infer it from context. The workflow verifies artifacts and tasks, syncs delta specs, extracts ADRs, and moves the change directory to openspec/changes/archive/YYYY-MM-DD-name.

What happens if tasks are incomplete when archiving a change?

Incomplete follow-up tasks do not block archiving; they remain in the archived tasks.md file. However, unaccepted slice acceptance tasks trigger a prompt where you can confirm acceptance, stop, or force-continue with the --force-legacy flag.

Does archiving a change update the main specs automatically?

Yes. If delta specs exist in the change directory, the workflow compares them with main specs and automatically syncs any additions, modifications, or removals before archiving. No manual merge step is required.

Why is my archive blocked by a code-truth gate error?

The archive is blocked when design.md, tasks.md, or specs reference technical symbols that do not exist in the actual code for completed scope. Fix it by syncing artifacts with the extend command or implementing the missing code with apply.

What are the limitations of the archive workflow?

It requires the openspec CLI and a conforming project structure with openspec/changes directories. Hard blockers like comment marker imbalance or phantom symbols must be resolved manually before archiving can proceed.