openspec-bulk-archive-change

Batch archive completed OpenSpec changes by selecting active changes and confirming a single prompt. The process reads active changes, validates statuses, resolves delta spec conflicts, and moves implemented changes to the archive folder with a date prefix.

Conflicting delta specs are resolved algorithmically during the batch archive process. The tool references the current codebase to determine which changes are actually implemented, ensuring only valid, non-conflicting specs are synchronized before archiving.

No, you cannot archive unimplemented changes. The batch archive process validates task statuses and references the current codebase to ensure only fully implemented changes are synchronized and moved to the archive directory.

OpenSpec batch archiving preserves metadata by applying a date prefix to the archived folders under openspec/changes/archive. It maintains all original change details while providing comprehensive status reporting for audit purposes.

No, manual conflict resolution is not required. The batch archive tool checks delta specs and resolves conflicts algorithmically, referencing the codebase to determine implemented changes before synchronizing and archiving.

Automated delta-spec synchronization occurs prior to archiving to maintain consistency across the codebase. This ensures the active specs reflect the implemented changes before they are permanently moved to the archive folder.