openspec-archive-change

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

Updated Jul 23, 2026
One-click install
npx skills add https://github.com/shrek-abaper/sap-nexus-agent --skill openspec-archive-change-shrek-abaper
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/shrek-abaper/sap-nexus-agent/tree/main/.comet/skills/skills/openspec-archive-change
Command: npx skills add https://github.com/shrek-abaper/sap-nexus-agent --skill openspec-archive-change-shrek-abaper

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 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, offers to sync specs, then moves the change to openspec/changes/archive/YYYY-MM-DD-<name>. ## Quick Start Ask the assistant to archive the completed OpenSpec change named add-user-auth, confirming any warnings about incomplete artifacts or tasks.

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 checks artifact and task completion, assesses delta spec sync state, then moves the change directory to openspec/changes/archive/YYYY-MM-DD-<name>.

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

The Skill counts incomplete tasks marked with '- [ ]' in tasks.md and displays a warning with the count. It asks for confirmation before proceeding, so archiving is never blocked but always informed.

Does archiving a change sync delta specs to main specs?▼

The Skill compares delta specs under openspec/changes/<name>/specs/ with main specs and shows a summary of pending changes. You can choose to sync via the openspec-sync-specs workflow 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 in 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?▼

The openspec CLI must be installed and the project must contain an openspec directory with changes. The Skill relies on 'openspec list --json' and 'openspec status --json' for change discovery and completion checks.