openspec-archive-change

To archive completed openspec changes, you provide the change name to initiate an automated workflow that moves the change to a date-stamped directory under openspec/changes/archive, preserving the .openspec.yaml metadata and folder structure for traceability.

Archiving an openspec change with incomplete tasks or artifacts triggers validation warnings before the process proceeds. The workflow prompts you to complete any unfinished items, ensuring only fully validated changes are moved to the archive directory.

Yes, the openspec CLI is required to manage change archiving. The archival workflow relies on the CLI to validate artifact statuses, assess delta specs, and physically move the change directory into the openspec/changes/archive path.

Yes, you can synchronize delta specs before archiving. The workflow offers an optional delta-spec synchronization assessment that generates a summarized report and provides an option to sync directly before moving the change to the archive.

Archived openspec changes are stored in a date-stamped directory format at openspec/changes/archive/YYYY-MM-DD-<name>. This structure preserves the original folder layout and .openspec.yaml metadata for easy retrieval and historical auditing.

The best way to prevent clutter from experimental openspec changes is to run an end-to-end archival workflow. This process validates completed tasks, syncs delta specs if needed, and safely moves the change to a dedicated archive directory.