openspec-bulk-archive-change

Batch-archiving multiple OpenSpec changes at once is achieved by selecting completed changes via prompts and moving them into a date-stamped archive folder. This single operation streamlines change management while preserving history and traceability.

Resolving delta-spec conflicts during change archiving involves inspecting the codebase to identify discrepancies and applying reconciled specs. The workflow ensures completed changes are moved into date-stamped directories without disrupting active development.

Yes, the OpenSpec CLI is required to batch-archive completed changes. The workflow relies on the CLI to read active changes, prompt for selection, perform conflict checks, and move archived changes into openspec/changes/archive/YYYY-MM-DD-<name> directories.

The date-stamped archive workflow structures directories by moving selected changes into openspec/changes/archive/YYYY-MM-DD-<name> folders. This organization preserves a clear history of when specific changes were archived across the codebase.

Yes, you can archive changes without disrupting active development. The batch-archive workflow preserves history and traceability by moving only selected completed changes into date-stamped archive paths, leaving active changes untouched.

Batch-archiving changes instead of archiving them individually streamlines change management by consolidating multiple completed changes into a single operation. This approach maintains date-stamped archive paths and resolves delta-spec conflicts efficiently across the codebase.