beads-workflowlisted

# 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