beads-workflow

<!-- TOC: Quick Start | Conversion Prompt | Polishing | bd → br Migration | Quality Checklist | Lifecycle Disciplines | When Beads Are Ready | Validation | References --> # Beads Workflow — From Plan to Actionable Tasks > **Core Principle:** "Check your beads N times, implement once" — where N is as many as you can stomach. > > Beads are so detailed and polished that you can mechanically unleash a big swarm of agents to implement them, and it will come out just about perfectly. This skill is the **conversion and shaping doctrine** — plan → beads, dependency/wave shaping, polish, lifecycle. It does NOT re-document the `br`/`bv` command surface: both binaries self-describe (`br --help`, `bv --help`, plus the beads_rust README and the `beads-br` / `beads-bv` skills). One hard rule worth front-loading: **never run bare `bv`** — it launches an interactive TUI; agents use `bv --robot-*` surfaces only. ## Quick Start ```bash br init # 1. Initialize beads in project # 2. Convert plan to beads (THE EXACT PROMPT below) # 3. Polish iteratively, 6-9 rounds, until steady-state br dep cycles # 4. Validate: must be empty bv --robot-insights # ...and check graph health bv --robot-next # 5. Begin implementation: get first bead ``` ## THE EXACT PROMPT — Plan to Beads Conversion ``` 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 ...