# 1. Initialize beads in project
br init

# 2. Convert plan to beads (see THE EXACT PROMPT below)

# 3. Polish iteratively
# Run polish prompt 6-9 times until steady-state

# 4. Validate
br dep cycles        # Must be empty
bv --robot-insights  # Check graph health

# 5. Begin implementation
bv --robot-next      # Get first bead

OK so now read ALL of [YOUR_PLAN_FILE].md; please take ALL of that and elaborate on it and use it to create a comprehensive and granular set of beads for all this with tasks, subtasks, and dependency structure overlaid, with detailed comments so that the whole thing is totally self-contained and self-documenting (including relevant background, reasoning/justification, considerations, etc.-- anything we'd want our "future self" to know about the goals and intentions and thought process and how it serves the over-arching goals of the project.). The beads should be so detailed that we never need to consult back to the original markdown plan document. Remember to ONLY use the `br` tool to create and modify the beads and add the dependencies. Use ultrathink.

OK so please take ALL of that and elaborate on it more and then create a comprehensive and granular set of beads for all this with tasks, subtasks, and dependency structure overlaid, with detailed comments so that the whole thing is totally self-contained and self-documenting (including relevant background, reasoning/justification, considerations, etc.-- anything we'd want our "future self" to know about the goals and intentions and thought process and how it serves the over-arching goals of the project.)  Use only the `br` tool to create and modify the beads and add the dependencies. Use ultrathink.

Reread AGENTS dot md so it's still fresh in your mind. Check over each bead super carefully-- are you sure it makes sense? Is it optimal? Could we change anything to make the system work better for users? If so, revise the beads. It's a lot easier and faster to operate in "plan space" before we start implementing these things!

DO NOT OVERSIMPLIFY THINGS! DO NOT LOSE ANY FEATURES OR FUNCTIONALITY!

Also, make sure that as part of these beads, we include comprehensive unit tests and e2e test scripts with great, detailed logging so we can be sure that everything is working perfectly after implementation. Remember to ONLY use the `br` tool to create and modify the beads and to add the dependencies to beads. Use ultrathink.

First read ALL of the AGENTS dot md file and README dot md file super carefully and understand ALL of both! Then use your code investigation agent mode to fully understand the code, and technical architecture and purpose of the project.  Use ultrathink.

We recently transformed a markdown plan file into a bunch of new beads. I want you to very carefully review and analyze these using `br` and `bv`.

br init                              # Initialize workspace
br create "Title" -t feature -p 1    # Create bead
br update <id> --status in_progress
br close <id> --reason "Done"
br reopen <id>                       # If needed

br dep add br-child br-parent        # child depends on parent
br dep remove br-child br-parent
br dep list <id>
br dep tree <id>
br dep cycles                        # MUST be empty!

br list                              # All beads
br ready                             # Actionable (not blocked)
br blocked                           # Blocked beads
br search "authentication"
br list --json                       # Machine-readable

br sync --flush-only                 # Export DB → JSONL
git add .beads/ && git commit -m "Update beads"

grep -c '`bd ' file.md        # must be 0
grep -c 'bd sync' file.md     # must be 0
grep -c 'br sync --flush-only' file.md  # must be > 0

bv --robot-triage                    # Full triage
bv --robot-next                      # Single top pick
bv --robot-plan                      # Parallel execution tracks
bv --robot-insights | jq '.Cycles'   # Check for cycles
bv --robot-insights | jq '.bottlenecks'

# Reserve files for bead
file_reservation_paths(..., reason="br-123")

# Announce work in thread
send_message(..., thread_id="br-123", subject="[br-123] Starting...")

# Close bead when done
br close br-123 --reason "Completed"
release_file_reservations(...)

git branch beads-sync main
git push -u origin beads-sync
br config set sync-branch beads-sync

br config list        # All settings
br dep cycles         # Must be empty
which br              # Verify br is installed

# Check for cycles (must be empty)
br dep cycles

# Check graph health
bv --robot-insights | jq '.Cycles'

# Verify all beads have descriptions
br list --json | jq '.issues[]? | select(.description == "")'