openspec-bulk-archive-change

To archive multiple completed changes at once, the bulk archive workflow collects active change sets, validates task completion, checks for delta spec conflicts, and moves confirmed items into the archive while preserving .openspec.yaml.

Handling spec conflicts during batch archiving requires detecting overlapping delta specs, checking implementation evidence in the codebase, and resolving the archive order when multiple changes touch the same capability.

Reviewing task completion before archiving involves checking openspec status, summarizing artifact readiness, and evaluating warnings to decide whether to archive everything or only the ready items in the batch.

Yes, you can batch archive openspec changes touching the same capability by using conflict-aware spec handling to detect overlaps, verify codebase implementation evidence, and resolve the correct ordered archive moves.

Batch archiving requires conflict detection across delta specs because multiple parallel changes may modify the same capability, meaning unordered moves risk overwriting implementation evidence and breaking codebase consistency.

You should avoid batch archiving completed openspec changes when task validation reveals incomplete artifacts or unresolved spec conflicts, requiring you to archive only the ready items instead of the entire batch.