writing-plans

Claim the implement step via beads_list and beads_update, decompose the spec into bite-sized TDD tasks, then create all task beads in one beads_create_list call in plan order. The beads themselves are the plan; no separate plan document is written.

Each step should be one action taking 2-5 minutes, such as writing a failing test, running it, implementing minimal code, and committing. Each task ends with an independently testable deliverable a reviewer could approve or reject on its own.

Yes. After the plan beads and approval gate are created, you hand off the implement step id to either subagent-driven-development in the same session or executing-plans in a parallel worktree session. Both read task beads directly via beads_show.

beads_create_list creates tasks sequentially so ids come out as parent.1 through parent.N matching plan order. Multiple create calls or out-of-order tasks break the id sequence and the plan-order display in bd list and the molecule widget.

Red flags include TBD or TODO markers, vague instructions like add appropriate error handling, test steps without actual test code, references to undefined types or functions, and tasks that duplicate lifecycle steps like spec approval already owned by the molecule.