openspec-bulk-archive-change

Batch archiving multiple OpenSpec changes requires the OpenSpec CLI to process completed changes in a single pass, prompting for selection and reporting outcomes for each change individually.

When batch archiving, the process detects delta-spec conflicts across selected changes and resolves them using codebase evidence, ensuring the final archived state accurately reflects the actual codebase.

Yes, the OpenSpec CLI is required to run the bulk archive operation. It facilitates prompting for change selection, resolving delta-spec conflicts, and moving completed changes to date-based archive paths.

The best way to keep change history clean is to batch archive completed changes in a single operation. This preserves the .openspec.yaml configuration and uses date-based archive paths to maintain traceability.

Yes, the bulk archive operation preserves the .openspec.yaml configuration file when archiving changes. It utilizes date-based archive paths to maintain historical traceability and reports outcomes for each change.

Batch archiving reduces manual work by processing multiple completed changes simultaneously, automatically detecting and resolving cross-change delta-spec conflicts using codebase evidence instead of handling each change individually.