openspec-archive-change

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

Updated Jan 31, 2026
One-click install
npx skills add https://github.com/thewoolleyman/personal-knowledge-base --skill openspec-archive-change-thewoolleyman
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/thewoolleyman/personal-knowledge-base/tree/main/.claude/skills/openspec-archive-change
Command: npx skills add https://github.com/thewoolleyman/personal-knowledge-base --skill openspec-archive-change-thewoolleyman

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Finalizing a completed change in an OpenSpec workflow involves several manual checks—verifying artifacts, 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 a sync before archiving. - Date-Stamped Archiving: Moves the change directory to openspec/changes/archive/YYYY-MM-DD-<name> with collision detection. - Use Case: After finishing implementation of a feature change, ask the assistant to archive it; the skill verifies everything is complete, syncs specs if needed, and files the change away with a summary. ## Quick Start Archive the completed change named add-user-auth and sync its delta specs before moving it to the archive.

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 a change name, or let it list active changes via `openspec list --json` so you can select one. It verifies artifacts and tasks, then moves the directory to `openspec/changes/archive/YYYY-MM-DD-<name>`.

What happens if tasks or artifacts are incomplete when archiving?▼

The skill displays a warning listing incomplete artifacts from `openspec status --json` and counts unchecked tasks in tasks.md. It asks for confirmation before proceeding, so archiving is never blocked but always informed.

Does archiving sync delta specs to the main specs?▼

Yes, if delta specs exist under `openspec/changes/<name>/specs/`, the skill compares them with main specs and shows a summary. You can choose to sync before archiving, archive without syncing, or cancel.

What if an archive with the same date and name already exists?▼

The archive fails with an error rather than overwriting. You are advised to rename the existing archive or use a different date for the target directory.

What are the requirements for using the OpenSpec archive workflow?▼

You need the openspec CLI installed and a project structured with `openspec/changes/` directories. The skill relies on `openspec list` and `openspec status` commands for change discovery and completion checks.