openspec-bulk-archive-change

Batch-archive multiple OpenSpec changes by running the CLI to list active changes, select finished ones, and reconcile delta spec requirements against main specs. The workflow detects cross-change capability conflicts and resolves them using codebase evidence before moving changes into a dated archive directory.

Spec conflict resolution detects capability-spec conflicts across selected changes, then investigates the codebase to decide whether to sync specs from one or multiple changes. It applies chronological ordering when both conflicting changes are already implemented, prompting the user for final selection and confirmation.

Yes, you can archive incomplete OpenSpec changes, but the batch workflow checks artifact completion, task checklist progress, and delta spec presence for each selected change. It displays warnings for incomplete changes and requires a single final confirmation before proceeding with the archive operation.

When an existing archive directory is encountered during batch archiving, the operation tracks it as a failure. The robust outcome reporting summarizes successes, failures, and skips, while detailing the spec-sync activity that completed successfully before the error occurred.

No, manual checks are unnecessary before batch archiving OpenSpec specs. The status consolidation feature automatically checks artifact completion, task checklist progress, and which delta spec requirements are present for each selected change, presenting warnings so you can make informed decisions.

The best way to reconcile delta spec requirements is using automated batch archiving with smart conflict resolution. It reads each change's tasks.md and delta specs, resolves conflicts via codebase evidence, and syncs specs from one or multiple changes based on chronological implementation order before final archiving.