spec-kitty-bulk-edit-classification

To safely plan a cross-codebase rename migration, you must route the request through an occurrence-classification guardrail. This ensures the rename target is explicitly named and a validated occurrence map is generated for approval before any modifications are made.

An occurrence map for bulk edit classification is a validated YAML artifact that categorizes every instance of a rename target into eight standard categories. It defines admissible per-category actions so a runtime gate can reliably check diff compliance and prevent silent breakage.

To prevent silent breakage during mechanical terminology or path swaps, activate a bulk edit guardrail during the specify or plan phase. This requires setting change_mode to bulk_edit and generating an occurrence map to classify every affected instance before implementation.

You need to set change_mode to bulk_edit during spec planning when a user request involves mechanical terminology, path, or key swaps across many files. This activates the occurrence-classification guardrail to validate the rename target and generate the required occurrence map.

A validated occurrence map for a rename migration must include all eight standard categories with admissible per-category actions defined. This validation constraint allows the runtime gate to reliably check admissibility and diff compliance before any code changes are applied.