openspec-archive-change

To archive a completed change, the workflow validates artifact and task completion, checks delta-spec synchronization, and moves the change to a persistent archive directory with a summary. You select the specific change, confirm any incomplete items, and the process records the archival outcome.

If incomplete tasks are detected during change archival, the workflow prompts for explicit user confirmation before proceeding. It enforces this selection step to ensure you intentionally acknowledge any unfinished artifacts before moving the change to the archive directory.

Yes, you need the OpenSpec CLI available in your environment to archive experimental changes. The archival workflow relies on this CLI to validate artifact statuses, check delta-spec synchronization, and move completed changes to a persistent archive.

Delta-spec synchronization checks run when delta specs exist for the change being archived. The workflow verifies synchronization status and optionally syncs the delta specs before moving the change to the archive directory, ensuring spec consistency.

The best way to keep active workspaces uncluttered is to archive completed changes to a persistent archive folder. This process moves finished changes out of the active experimental workflow, preserving a clear history while validating artifact and task completion.

No, you cannot skip validation; the workflow checks for artifact and task completion before archiving. If incomplete items are found, it prompts for explicit confirmation, ensuring you acknowledge the status before the change is moved to the archive.