openspec-bulk-archive-change

Batch archiving OpenSpec changes detects spec conflicts by capability and resolves them using codebase evidence. It syncs delta specs to main specs only when implementation is found, applying chronological order when both sides are implemented.

Bulk archive operations use failure isolation to ensure that if one change fails, others continue processing. The tool produces a consolidated status table summarizing archived, skipped, and failed outcomes per change.

Implementation-aware spec syncing checks your codebase for corresponding implementation before applying delta specs to main specs. This ensures only verified deltas are synced, preventing unimplemented changes from altering your main specs.

Yes, the openspec CLI is required. Bulk archiving relies on openspec CLI commands and JSON parsing to inspect delta specs, detect conflicts by capability, and execute date-based move operations into an archive directory.

Conflict detection identifies overlapping spec modifications by capability across selected changes. It resolves conflicts using implementation-based evidence from your codebase and syncs applicable deltas in chronological order when both sides are implemented.

Use a bulk archive tool to select multiple completed changes from a prompted multi-select list. It prepares a per-change outcome plan, handles task completion validation, and moves change directories into an archive with clear reporting.