openspec-bulk-archive-change

To archive multiple completed spec changes at once, this Skill automates batch archiving by resolving spec conflicts through codebase analysis, handling artifact status, task completion, and delta spec synchronization before moving changes to an archive directory.

Automatic spec conflict resolution when archiving parallel feature updates works by intelligently checking the codebase to merge specifications and resolve conflicts based on the actual code implementation of the completed changes.

Yes, you can use bulk archiving for completed changes that touch the same capabilities, as the Skill automatically resolves spec conflicts by analyzing the codebase to ensure correct specification merging before moving changes to an archive directory.

The best way to handle delta spec synchronization before moving changes to an archive directory is to use this bulk archiving automation, which manages artifact status, task completion, and conflict resolution in a single operation.

No, the bulk archiving process does not require manual git version control interventions, as it intelligently analyzes the codebase and automates the resolution of spec conflicts during the batch archiving of multiple completed changes.

During batch spec archiving, artifact status and task completion records are automatically handled and synchronized by the Skill, ensuring delta specs are correctly merged before moving the completed changes to an archive directory.