openspec-archive-change

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Finalizing a completed change in an OpenSpec-driven workflow involves several manual checks: verifying artifact completion, confirming tasks are done, syncing delta specs into main specs, and moving the change directory into a dated archive. This Skill automates that entire finalization sequence so nothing is archived prematurely or left out of sync. ## Core Features & Use Cases - Guided change selection: Lists active changes via openspec list --json and prompts the user to pick one instead of guessing. - Completion verification: Checks artifact status with openspec status --json and counts incomplete tasks in tasks.md, warning before archiving unfinished work. - Delta spec sync assessment: Compares delta specs against main specs, summarizes pending changes, and optionally triggers the openspec-sync-specs workflow before archiving. - Use Case: After finishing implementation of a feature change, ask the assistant to archive it; the Skill verifies all artifacts and tasks, syncs specs if needed, and moves the change to openspec/changes/archive/YYYY-MM-DD-<name>/. ## Quick Start Archive the completed OpenSpec change for the feature we just finished implementing.

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?▼

Run the archive workflow, which lists active changes via openspec list --json and prompts you to select one. It then verifies artifacts and tasks, optionally syncs delta specs, and moves the change to openspec/changes/archive/YYYY-MM-DD-<name>/.

What happens if I archive a change with incomplete tasks?▼

The workflow counts tasks marked with - [ ] in tasks.md and displays a warning showing how many are incomplete. You are asked to confirm before proceeding, so archiving is never blocked but always informed.

Does archiving sync delta specs to the main specs automatically?▼

Not automatically. The workflow compares delta specs under openspec/changes/<name>/specs/ with main specs, shows a summary of pending changes, and lets you choose to sync now via the openspec-sync-specs skill or archive without syncing.

What if the archive target directory already exists?▼

The archive fails with an error if a directory named YYYY-MM-DD-<change-name> already exists under openspec/changes/archive/. You are advised to rename the existing archive or use a different date.

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 change should have completed implementation, though the workflow only warns rather than blocks on incomplete artifacts or tasks.