openspec-archive-change

To archive completed openspec changes, the workflow validates artifacts via openspec status, scans tasks from tasks.md, assesses delta specs, then moves the change directory to a date-stamped archive folder while preserving .openspec.yaml.

Archiving a change in openspec moves the completed change directory to openspec/changes/archive/YYYY-MM-DD-<name>, preserving the original .openspec.yaml file for auditability, traceability, and easy retrieval.

Yes, you need the openspec CLI installed to archive change directories because the archival process relies on running openspec status to verify artifact and task completeness before moving files.

If openspec artifacts or tasks are incomplete, the archival guardrails prevent the change from moving to the archive folder, ensuring only fully validated and implemented changes are archived.

Yes, the prompt-driven archival workflow lets you decide whether to sync delta specs before moving the completed change directory to the date-stamped archive path for proper traceability.

The best way to ensure traceability is archiving with a date-stamped path and preserving the original .openspec.yaml file, which maintains full auditability of completed artifacts and delta specs.