openspec-archive-change

Archives completed OpenSpec changes with artifact, task, and spec sync verification.

1|Updated May 19, 2026
One-click install
npx skills add https://github.com/thomasmartinsen/talks --skill openspec-archive-change-thomasmartinsen
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/thomasmartinsen/talks/tree/main/20260519%20-%20Agentic%20engineering/weather-app-demo/.claude/skills/openspec-archive-change
Command: npx skills add https://github.com/thomasmartinsen/talks --skill openspec-archive-change-thomasmartinsen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Finalizing a completed change in an OpenSpec workflow involves several manual checks—verifying artifact completion, confirming tasks are done, syncing delta specs, and moving directories—which is error-prone when done by hand. ## Core Features & Use Cases - Guided Change Selection: Lists active changes via openspec list --json and prompts the user to pick one, never auto-selecting. - Completion Verification: Checks artifact status with openspec status --json and counts incomplete tasks in tasks.md, warning before proceeding. - Delta Spec Sync Assessment: Compares delta specs against main specs and optionally triggers the openspec-sync-specs workflow before archiving. - Use Case: After finishing implementation of a feature change, run this Skill to confirm all artifacts and tasks are complete, sync spec updates, and move the change into openspec/changes/archive/YYYY-MM-DD-<name>/. ## Quick Start Archive the completed change "add-user-auth" after verifying its artifacts, tasks, and spec sync status.

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 an optional change name; if omitted, it lists active changes via openspec list --json and prompts you to select one. It then verifies artifacts and tasks before moving the change to openspec/changes/archive/YYYY-MM-DD-<name>/.

How to sync delta specs before archiving a change?

The workflow compares delta specs in openspec/changes/<name>/specs/ against main specs and shows a summary of additions, modifications, and removals. You can choose to sync via the openspec-sync-specs skill or archive without syncing.

What happens if tasks are incomplete when archiving a change?

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

Does archiving a change require the openspec CLI?

Yes, the workflow requires the openspec CLI to run openspec list --json and openspec status --change <name> --json for change discovery and artifact completion checks. Without it, these verification steps cannot run.

What happens if the archive target directory already exists?

The archive fails with an error if a directory named YYYY-MM-DD-<change-name> already exists in openspec/changes/archive/. It suggests renaming the existing archive or using a different date.