openspec-archive-change

To archive completed openspec changes, the workflow verifies artifacts, tasks, and delta specs before moving the change directory into a dated archive, preserving configuration files and ensuring traceability.

When archiving an openspec change with incomplete artifacts or tasks, the workflow detects the issue using list and status outputs, then requests explicit user confirmation before proceeding with the archive operation.

Yes, you can optionally trigger a spec sync before archiving. The workflow compares change delta specs with main specs, summarizes additions, edits, and removals, and optionally initiates the sync.

Yes, the openspec CLI is required for list and status operations to verify completion. The workflow also needs filesystem access to move directories and preserve configuration during the archive process.

The archive process creates a dated archive directory to prevent naming collisions and provides clear error handling if conflicts occur, ensuring the change directory is moved safely without data loss.

The workflow prompts you to pick an active change to prevent accidental auto-selection, ensuring you explicitly confirm the correct experimental openspec change before it is archived and finalized.