openspec-bulk-archive-change

You can batch-archive multiple OpenSpec changes by running a single operation that processes active changes, resolves conflicts, and stores them in date-stamped archive folders. This simplifies batch maintenance and ensures consistent archiving.

Batch archiving detects overlapping delta specs across chosen changes and resolves conflicts based on codebase evidence. It enforces defined conflict resolution rules and generates optional resolution notes for each archived change.

Yes, the batch archival operation preserves existing YAML metadata while archiving changes under date-stamped directories. This ensures historical configuration data remains intact during the batch maintenance process.

The batch archiving process generates per-change status reports and consolidated audit-ready output. These reports include archival status and optional resolution notes for conflicts detected during the operation.

Batch archiving is best when you have multiple ready-to-archive OpenSpec changes and need consistent processing. It evaluates artifacts, tasks, and delta specs together, resolving conflicts in a single run rather than manually.

Yes, the batch archival workflow evaluates artifacts, tasks, and delta specs for chosen changes before archiving. This ensures only completed changes are processed and moved to the archive directory.