openspec-archive-change

Archiving completed changes in an openspec workflow involves using the openspec CLI to list changes, verify artifact and task completion status, and securely store the finalized change. The process prompts you to select a specific change if one is not explicitly named.

To check completion status before archiving a change, the openspec CLI verifies that all related artifacts and tasks are complete. The workflow assesses the sync state of any delta specs and prompts the user to resolve issues before finalizing the archive.

Yes, you need the openspec CLI to archive changes. The Skill requires this dependency to execute commands for listing changes, checking completion status, handling user selection, and securely storing the archived changes in the experimental workflow.

When delta specs exist during the change archiving process, the Skill assesses their sync state. It then prompts you accordingly to ensure the delta specs are properly synchronized before the change is finalized and moved to the archive location.

To select a specific change to archive, you provide the change name directly in your request, such as 'example-change'. If a name is not specified, the Skill prompts you to select the desired change from a list generated by the openspec CLI.