Skip to content

create-beads: add an independence heuristic for the epic-vs-single-bead choice #2

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
fkberthold wants to merge 1 commit into
base: main
Choose a base branch
from
Open

create-beads: add an independence heuristic for the epic-vs-single-bead choice #2

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions skills/create-beads/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -20,6 +20,12 @@ bd create "Task 1" --parent <epic-id> -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
Expand Down