openspec-archive-change

Archive a completed experimental workflow change by validating artifact completion and task progress, then moving the change directory into a date-stamped archive folder. This process ensures a reliable handoff from experimental execution to long-term record keeping without losing key files.

When incomplete artifacts or tasks are detected during change archival, the workflow implements guardrails that prompt you before proceeding. It checks artifact completion via openspec status and scans tasks.md to flag any incomplete checklist items.

Spec synchronization assesses delta specs for the change by summarizing required adds, modifications, removals, and renames. It then asks whether to sync the delta specs with the main specs or archive the change without syncing.

Yes, archiving experimental changes requires openspec CLI availability. The archival workflow uses JSON status parsing from the CLI to validate artifact completion and tasks.md scanning before moving the change directory.

No, the safe archival workflow fails if the target date-stamped archive directory already exists. This prevents overwriting existing archived changes in the openspec/changes/archive path.

Validate task completion by reading a tasks file, typically tasks.md, to detect incomplete checklist items. The workflow prompts you before proceeding if any incomplete tasks are found during the archival validation phase.