openspec-archive-change

Archives completed OpenSpec changes after verifying artifact and task completion.

Updated Mar 17, 2026

Search Tags:#workflow #cli #archive #change management #spec-driven development #openspec

Ready to run

npx skills add https://github.com/beliciobcardoso/mcp-postgres --skill openspec-archive-change-beliciobcardoso

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/beliciobcardoso/mcp-postgres/tree/main/.qwen/skills/openspec-archive-change
Command: npx skills add https://github.com/beliciobcardoso/mcp-postgres --skill openspec-archive-change-beliciobcardoso

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 - Completion Verification: Checks artifact status via `openspec status --json` and counts incomplete tasks in `tasks.md` before archiving. - Delta Spec Sync Assessment: Compares delta specs against main specs and offers to sync them before archiving. - Safe 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 prompts you to pick the change, warns about incomplete items, optionally syncs specs, and archives with a dated folder name. ## Quick Start Ask the assistant to archive the completed OpenSpec change and confirm the prompts it presents.

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 change in OpenSpec?▼

Invoke the archive workflow and optionally provide a change name. The skill runs openspec list to let you select an active change, verifies artifacts and tasks, then moves the directory to openspec/changes/archive with a date-prefixed name.

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

The skill displays a warning listing incomplete artifacts or the count of unfinished tasks, then asks for confirmation. Archiving is not blocked; it proceeds only after you explicitly confirm you want to continue.

Does archiving sync delta specs to the main specs?▼

If delta specs exist under the change's specs directory, 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 when the target directory already exists. You are advised to rename the existing archive or run on a different date, since the target name is generated as YYYY-MM-DD-<change-name>.

What are the requirements to use 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 with JSON output for selection and completion checks.