bd-to-br-migration_skill

Overview

This skill migrates documentation and commands from bd (beads) to br (beads_rust) with deterministic, ordered transforms. It focuses on mechanical find-and-replace plus inserting required git steps after every sync, ensuring agents and docs remain consistent and functional. Use this to produce verified migrations that pass built-in checks.

How this skill works

The skill applies a strict sequence of edits: rename headers, insert a non-invasive note, convert supported bd commands to br, replace bd sync with br sync --flush-only and add git add/.commit steps, convert issue IDs, and update links. It removes daemon, auto-commit, hook, and RPC references while preserving allowed patterns like SQLite/WAL cautions and priority semantics. A verification loop with grep-based checks ensures no bd remnants remain.

When to use it

• Updating AGENTS.md or any single file mentioning bd (beads)
• Converting bd command examples to br equivalents in docs
• Replacing bd sync occurrences with br sync --flush-only and adding git steps
• Performing beads → beads_rust migration across a small set of files
• Verifying an existing migration for leftover bd references

Best practices

• Apply transforms in the exact order specified—order is important
• Always run the provided verification scripts after editing
• Insert the non-invasive note immediately after any beads section header
• Add git add .beads/ and git commit -m "sync beads" after every br sync occurrence
• Do not remove SQLite/WAL cautions, bv integration, or priority system notes

Example use cases

• Migrate a single AGENTS.md file to br with exact command replacements and verification
• Batch-process under 10 files sequentially using the same deterministic transforms
• Prepare docs for agents by removing daemon, RPC, and auto-commit assumptions
• Verify a previously attempted migration and locate leftover bd references
• Convert session end examples that previously relied on bd auto-commits to explicit git steps