/plan

Breaks down a goal into beads issues. Use when work spans multiple sessions or has dependencies.

Usage

Text Only

/plan "your goal"

What's Different from L2

At L3, planning creates trackable issues: - Issues stored in .beads/ database - Dependencies tracked (what blocks what) - Progress visible with bd ready, bd list

Steps

1. Claude researches what's needed
2. Claude creates issues with bd create
3. Claude sets dependencies with bd dep add
4. Plan saved to .agents/plans/

Output

Text Only

Created 5 issues for "Add user authentication":
  [P1] agentops-abc: Set up auth middleware
  [P1] agentops-def: Create login endpoint
  [P2] agentops-ghi: Add session storage (depends on abc)
  [P2] agentops-jkl: Create logout endpoint (depends on def)
  [P3] agentops-mno: Add tests (depends on ghi, jkl)

Ready to work: agentops-abc, agentops-def

Example

Text Only

You: /plan "add dark mode support"

Claude: I'll research and plan dark mode implementation.

[Research existing theme handling...]

Creating issues:

$ bd create --title "Add theme context provider" --priority 1
Created: agentops-xyz

$ bd create --title "Create dark mode toggle" --priority 2
Created: agentops-abc

$ bd dep add agentops-abc agentops-xyz

Plan saved to: .agents/plans/2025-01-15-dark-mode.md

Next: `bd ready` to see what's unblocked, then `/implement`

Next

• bd ready - See unblocked issues
• /implement agentops-xyz - Work on specific issue