openspec-archive-change

To archive completed experimental workflow changes safely, this skill validates artifact completion status via openspec-cn CLI, checks tasks files for unfinished items, and moves the change directory into a date-stamped archive folder to prevent data loss.

When delta specs differ from main specifications during archiving, the skill detects incremental spec changes and prompts the user to choose between synchronizing with main capability specs via a subagent or archiving the change without syncing.

Yes, you need the openspec-cn CLI available to finalize and archive spec changes, as the workflow relies on it to list changes and check completion status by parsing JSON output for guardrailed validation.

The archiving process handles directory name collisions by moving the experimental change into openspec/changes/archive/YYYY-MM-DD-<name> with safe naming conventions that prevent overwriting any existing archived artifacts.

You can attempt to archive an experimental change with unfinished tasks, but the skill performs guardrailed completion checks by reading tasks.md and will issue warnings if artifacts are not marked done or if unfinished items are detected.