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.

What Are Beads?

Beads are epics/tasks/subtasks with dependency structure, optimized for AI coding agents. Think of them as Jira or Linear, but designed for machines.

Key properties:

• Self-contained — Never need to refer back to the original markdown plan
• Self-documenting — Include background, reasoning, justifications, considerations
• Dependency-aware — Explicit structure of what blocks what
• Rich descriptions — Long markdown comments, not short bullet points

Why Beads Work

┌─────────────────────────────────────────────────────────────┐
│ MARKDOWN PLAN (~3,500 lines)                                │
│   └─► Fits in context window                                │
│   └─► Models reason about entire system at once             │
├─────────────────────────────────────────────────────────────┤
│                    ↓ CONVERT TO BEADS ↓                     │
├─────────────────────────────────────────────────────────────┤
│ BEADS (distributed tasks)                                   │
│   └─► Each bead is self-contained                           │
│   └─► Any agent can pick up any bead                        │
│   └─► BV (Beads Viewer) handles prioritization              │
│   └─► Agent Mail handles coordination                       │
└─────────────────────────────────────────────────────────────┘

Converting Plans to Beads

THE EXACT PROMPT — Plan to Beads Conversion (Claude Code + Opus 4.5)

OK so now read ALL of PLAN_TO_CREATE_GH_PAGES_WEB_EXPORT_APP.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 `bd` tool to create and modify the beads and add the dependencies. Use ultrathink.

Note: Replace PLAN_TO_CREATE_GH_PAGES_WEB_EXPORT_APP.md with your actual plan filename.

Alternative Shorter Version

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 `bd` tool to create and modify the beads and add the dependencies. Use ultrathink.

What This Creates

• Tasks and subtasks with clear scope
• Dependency links (what must complete before what)
• Detailed descriptions with:
  • Background context
  • Reasoning and justification
  • Technical considerations
  • How it serves project goals

Polishing Beads

Why Polish?

Even after initial conversion, beads continue to improve with review. You get incremental improvements even at round 6+.

THE EXACT PROMPT — Polish Beads (Full Version)

Reread AGENTS dot md so it's still fresh in your mind. Then read ALL of PLAN_TO_CREATE_GH_PAGES_WEB_EXPORT_APP.md . Use ultrathink. 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 the 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. It's critical that EVERYTHING from the markdown plan be embedded into the beads so that we never need to refer back to the markdown plan and we don't lose any important context or ideas or insights into the new features planned and why we are making them.

THE EXACT PROMPT — Polish Beads (Standard Version)

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 `bd` tool to create and modify the beads and to add the dependencies to beads. Use ultrathink.

Polishing Protocol

1. Run the polishing prompt
2. Review changes
3. Repeat until steady-state (typically 6-9 rounds)
4. If it flatlines, start a fresh CC session
5. Optionally have Codex with GPT 5.2 do a final round

Fresh Session Technique

If polishing starts to flatline, start a brand new Claude Code session:

THE EXACT PROMPT — Re-establish Context

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.

THE EXACT PROMPT — Then Review Beads

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

Then follow up with the standard polish prompt.

Cross-Model Review

For extra polish, have different models review the beads:

Bead Quality Checklist

Before implementation, verify each bead:

• Self-contained — Can be understood without external context
• Clear scope — One coherent piece of work
• Dependencies explicit — Links to blocking/blocked beads
• Testable — Clear success criteria
• Includes tests — Unit tests and e2e tests in scope
• Preserves features — Nothing from the plan was lost
• Not oversimplified — Complexity preserved where needed

Using bd (Beads CLI)

Basic Commands

# Initialize beads in project
bd init

# Create a new bead
bd create "Implement user authentication" -t feature -p 1

# Add dependencies
bd depend BD-123 BD-100  # BD-123 depends on BD-100

# Update status
bd update BD-123 --status in_progress

# Close a bead
bd close BD-123 --reason "Completed and tested"

# List ready beads (no blockers)
bd ready --json

Robot Mode for Agents

# Get triage recommendations
bv --robot-triage

# Get the single top pick
bv --robot-next

# Get parallel execution tracks
bv --robot-plan

# Get graph insights (PageRank, bottlenecks, cycles)
bv --robot-insights

CRITICAL: Never run bare bv — it launches interactive TUI. Always use --robot-* flags.

Integration wit