openspec-archive-change

Archive completed openspec changes with artifact, task, and spec sync verification.

Updated Nov 7, 2023
One-click install
npx skills add https://github.com/lstellway/nixfiles --skill openspec-archive-change-lstellway
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-archive-change
Source: https://github.com/lstellway/nixfiles/tree/main/modules/home-manager/claude/skills/openspec-archive-change
Command: npx skills add https://github.com/lstellway/nixfiles --skill openspec-archive-change-lstellway

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Finalizing a completed change in an openspec workflow involves several manual checks—verifying artifacts are done, confirming tasks are complete, and deciding whether delta specs need syncing—before safely moving the change into the 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, never guessing or auto-selecting. - Completion verification: Checks artifact status with openspec status --json and counts incomplete tasks in tasks.md, warning the user before proceeding. - Delta spec sync assessment: Compares delta specs against main specs, summarizes pending changes, and optionally triggers the openspec-sync-specs workflow before archiving. - Safe archiving: Moves the change directory to openspec/changes/archive/YYYY-MM-DD-<name> with collision detection to prevent overwriting existing archives. - 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, and produces a dated archive entry with a completion summary. ## Quick Start Archive my completed openspec change and sync its delta specs to the main specs first.

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 a change name, or let it list active changes via openspec list --json so you can select one. The change directory is moved to openspec/changes/archive/YYYY-MM-DD-<name> after verification checks.

What happens if artifacts or tasks are incomplete when archiving?

The workflow checks artifact status with openspec status --json and counts incomplete tasks marked with - [ ] in tasks.md. It displays a warning and asks for confirmation before proceeding, but does not block the archive.

Does archiving sync delta specs to the main specs?

If delta specs exist under openspec/changes/<name>/specs/, the workflow compares them 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 happens if an archive with the same date and name already exists?

The archive fails with an error rather than overwriting the existing entry. You are advised to rename the existing archive or use a different date before retrying.

What are the requirements for using the openspec archive workflow?

You need the openspec CLI installed and a project structured with an openspec/changes directory. The change being archived should have gone through the experimental workflow with artifacts tracked by openspec status.