openspec-bulk-archive-change

Batch-archiving completed changes involves analyzing active changes, detecting delta-spec conflicts, resolving them via codebase evidence, and executing a user-guided archival operation that preserves repository configuration and history.

Delta-spec conflict resolution identifies overlapping modifications between active changes, then guides resolution by inspecting chronological order and codebase evidence before proceeding with the batch archival.

Yes, you can archive multiple active changes while preserving configuration and history, as the workflow consolidates records into a single archived entry with per-change status reporting for artifacts and tasks.

Batch archiving requires explicit user selection and a final confirmation to prevent accidental archival, but it does not require individual manual confirmation for every single change within the selected batch.

The best way to handle conflicts when consolidating active changes is to automatically detect delta-spec conflicts and guide resolution based on codebase evidence and chronological order before archiving.

Per-change status reporting provides visibility into artifacts, tasks, and spec touchpoints before confirming the batch operation, ensuring you verify all dependencies and impacts are safely resolved prior to archival.