openspec-bulk-archive-change

To batch-archive multiple OpenSpec changes, you can initiate a single operation that validates delta specs, stages files, and archives completed changes into date-stamped folders while preserving metadata and the .openspec.yaml configuration.

Conflict resolution during OpenSpec archiving is handled through a guided workflow that performs codebase lookups to determine actual implementations, using code evidence to resolve synchronization conflicts across parallel changes.

You need batch archiving when managing projects with parallel OpenSpec changes that require coordinated archiving, conflict-aware delta-spec synchronization, and consistent release history without manual individual archiving chores.

Yes, batch archiving preserves project metadata and the .openspec.yaml configuration file by archiving changes into date-stamped folders while maintaining consistent history across all staged delta specs.

The OpenSpec batch archive workflow determines actual code implementations by performing codebase lookups during the validation and staging process, ensuring delta specs synchronize with the real code evidence before archiving.

Archiving OpenSpec changes with conflicts follows a guided workflow with prompts and conflict resolution based on code evidence, ensuring synchronization issues are addressed before changes are archived into date-stamped folders.