From e91aa96249786821982668fd3c4df473603efe0c Mon Sep 17 00:00:00 2001 From: Frank Berthold Date: Fri, 29 May 2026 11:32:09 -0700 Subject: [PATCH] Add independence heuristic for epic-vs-single-bead choice create-beads framed the multi-task/small-feature split by size only. Add a short heuristic prompting the independence question (shared files / sequential dependency) at creation time, so independent work becomes sibling tasks under an epic that bd ready can surface in parallel, and coupled work stays a single bead. Tracked downstream as loom-7bn. --- skills/create-beads/SKILL.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/skills/create-beads/SKILL.md b/skills/create-beads/SKILL.md index ce75fcc..c43a0f4 100644 --- a/skills/create-beads/SKILL.md +++ b/skills/create-beads/SKILL.md @@ -20,6 +20,12 @@ bd create "Task 1" --parent -d "What to do, files to touch" bd create "Task title" -d "Description" ``` +**Epic or one bead?** When you have 2+ candidate items, ask if they're *independent* — no shared files, no sequential dependency: +- **Independent** → sibling tasks under one epic. `bd ready` surfaces them in parallel, so an executor can dispatch them concurrently. +- **Coupled** (shared files, or one needs another's outcome) → a single bead with steps. Splitting them just creates dependency edges you have to manage. + +Default to one bead when unsure — it's cheaper to split a bead later than to merge two. + ## Task Guidelines - Bite-sized: 2-5 minutes each