bd-to-br-migration

Migrate bd documentation to br with deterministic transforms and verification.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/Dunc4nJ/agent-skills --skill bd-to-br-migration-dunc4nj
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bd-to-br-migration
Source: https://github.com/Dunc4nJ/agent-skills/tree/main/skills/bd-to-br-migration
Command: npx skills add https://github.com/Dunc4nJ/agent-skills --skill bd-to-br-migration-dunc4nj

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Migrate documentation references from the bd (beads) system to br (beads_rust) with a deterministic, verifiable workflow to prevent broken AGENTS.md references during upgrades.

Core Features & Use Cases

  • Ordered, deterministic transforms mean updates happen in a fixed sequence: headers, notes, command mappings, sync behavior, and ID replacements.
  • Removes deprecated bd-specific references (daemon, RPC, auto-commit assumptions) and updates issue IDs from bd-### to br-###, ensuring consistency across files.
  • Supports single-file migrations via the exact prompt and batch migrations using a bulk strategy with subagents, including built-in verification scripts.
  • Ideal for updating AGENTS.md files in a codebase, migrating documentation across many projects, or validating migration in a controlled environment with greps and verification scripts.

Quick Start

Execute the exact bd-to-br migration workflow on an AGENTS.md file or a batch of files and verify results with the provided scripts.

Frequently Asked Questions about bd-to-br-migration

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I migrate beads documentation references to beads_rust without breaking AGENTS.md files?

Migrate beads documentation to beads_rust by applying a deterministic transform workflow with a strict order: headers, notes, command mappings, sync behavior, and ID replacements, which prevents broken AGENTS.md references during upgrades.

What is the best way to batch migrate bd-### issue IDs to br-### across multiple projects?

Batch migrating bd-### issue IDs to br-### uses a bulk strategy with optional subagent orchestration, removing deprecated bd-specific daemon and RPC references while ensuring cross-file consistency through built-in discovery and validation.

Does the bd to br migration process include built-in verification scripts?

Yes, the bd to br migration process includes built-in verification scripts and greps to validate results, ensuring deterministic transforms and post-edits maintain reference consistency in a controlled environment.

Can I use this deterministic migration workflow for single-file AGENTS.md updates?

Yes, you can use this deterministic migration workflow for single-file AGENTS.md updates by executing the exact migration prompt, which applies ordered transforms and requires frontmatter with name and description fields.

What deprecated references are removed during a beads to beads_rust migration?

During a beads to beads_rust migration, deprecated bd-specific references including daemon, RPC, and auto-commit assumptions are removed, while issue IDs are updated from bd-### to br-### to ensure consistency.