bd-to-br-migration

Migrating markdown documentation from beads to beads_rust involves running a migration tool on target files to apply deterministic section, command, and ID transforms, followed by executing verification scripts to confirm completion.

Yes, you can batch migrate multiple markdown files from bd to br workflows using the skill's batch migration mode, which provides clear reporting and rollback guidance for project-wide consistency across all updated references and IDs.

A bd to br migration updates exact section and header transformations, command mappings, sync behavior, and ID/link updates, converting all beads references to their beads_rust equivalents.

To verify remaining bd references after migrating to beads_rust, run the built-in discovery and verification scripts which identify leftover bd patterns and validate that br references are correctly applied across the project.

The bd-to-br migration does not require external dependencies, relying solely on the skill's SKILL.md presence and its internal scripts for executing deterministic transforms and verification utilities.

The best way to handle rollback for a beads to beads_rust migration is to follow the batch migration guidelines, which provide clear reporting and rollback guidance to safely revert deterministic transforms if verification fails.