Next - Pick Your Next Bead
Help select the next bead to work on based on readiness and user preferences.
When to Use
- Starting a new work session
- Finished a task and need to pick the next one
- Want to see what's available to work on
- Need help prioritizing between multiple options
Usage
/next # Show ready beads, ranked by suitability
/next task # Auto-pick the next most suitable task and start it
/next quick # Auto-pick an easy win task and start it
/next <bead-id> # Start working on specific bead
What This Skill Does
Find Ready Work
- Run
bd ready to get unblocked tasks
- Filter out beads that are blocked by others
- Show current in-progress work if any
Rank by Suitability
- Apply priority ranking algorithm (see below)
- Bugs generally rank higher than features at same priority
- Epics rank lower (they represent larger work)
Present Options
- Show top 5 candidates with key details
- Include: ID, title, priority, type, age
- Ask user to pick or provide different criteria
Start Work
- Mark selected bead as in_progress
- Show full bead details
- Suggest first steps if description includes them
Examples
# Show ready work ranked by suitability
/next
# Auto-pick and start the next most suitable task
/next task
# Auto-pick an easy win (quick task)
/next quick
# Start a specific bead
/next gauge-abc
Output Format
## Ready to Work (5 of 12 open)
| # | ID | Pri | Type | Parent/Subs | Title |
|---|-----------|-----|---------|-------------|--------------------------------|
| 1 | gauge-abc | P1 | bug | - | Fix login timeout issue |
| 2 | gauge-def | P2 | feature | 3 subtasks | Add export to CSV |
| 3 | gauge-ghi | P2 | task | gauge-def | Update dependencies |
| 4 | gauge-jkl | P3 | feature | - | Dark mode toggle |
| 5 | gauge-mno | P3 | task | 2 subtasks | Refactor auth service |
Currently in progress: gauge-xyz "Implement caching layer"
Which would you like to work on? (1-5, or specify ID, or "task" to auto-pick)
Implementation
When invoked:
Check for current open, not in-progress elsewhere, work:
bd list --status=open
Get ready (unblocked) beads:
bd ready
Parse command argument:
- (none): Show ranked list, ask user to pick
task: Auto-select top-ranked bead and start it
quick: Auto-select an easy win task and start it
<bead-id>: Start that specific bead
If specific bead ID provided:
bd show <id>
bd update <id> --status=in_progress
Otherwise, present top 5 options and ask user to choose
On selection:
- Mark as in_progress
- Show full details with
bd show
- If bead has description with steps, highlight first step
Handling Edge Cases
- No ready beads: Show blocked beads and what's blocking them
- All in progress: Warn about context switching, show current work
- Invalid ID: Show error and list valid options
- User says "skip": Show next 5 options
Priority Ranking Algorithm
Rank ready beads in this order (first match wins):
| Rank |
Criteria |
| 1 |
Any P0 issue (any type) |
| 2 |
P1 bug |
| 3 |
P2 bug |
| 4 |
P1 feature or task |
| 5 |
P1 epic |
| 6 |
P2 feature or task |
| 7 |
P3 bug, feature, or task |
| 8 |
P2 epic |
| 9 |
P3 epic |
| 10 |
Any other non-P4 issue |
Note: P4 items are backlog and not shown by default.
Quick Task Heuristics
When /next quick is used, prefer:
- Type: task > bug > feature (tasks are usually smaller)
- Priority: P3 > P2 > P1 (lower priority = less complex)
- Exclude epics (too large for quick wins)
- Title keywords: "fix", "update", "add" > "implement", "refactor", "redesign"
1---
2name: next
3description: >
4 Pick the next bead to work on. Shows ready tasks (no blockers), applies user
5 preferences for ordering (priority, type, recency), and helps select work.
6allowed-tools: "Read,Bash(bd:*),AskUserQuestion"
7version: "1.0.0"
8author: "flurdy"
9metadata:
10 source: https://skillmd.com/skills/majiayu000/next
11---
12
13# Next - Pick Your Next Bead
14
15Help select the next bead to work on based on readiness and user preferences.
16
17## When to Use
18
19- Starting a new work session
20- Finished a task and need to pick the next one
21- Want to see what's available to work on
22- Need help prioritizing between multiple options
23
24## Usage
25
26```
27/next # Show ready beads, ranked by suitability
28/next task # Auto-pick the next most suitable task and start it
29/next quick # Auto-pick an easy win task and start it
30/next <bead-id> # Start working on specific bead
31```
32
33## What This Skill Does
34
351. **Find Ready Work**
36 - Run `bd ready` to get unblocked tasks
37 - Filter out beads that are blocked by others
38 - Show current in-progress work if any
39
402. **Rank by Suitability**
41 - Apply priority ranking algorithm (see below)
42 - Bugs generally rank higher than features at same priority
43 - Epics rank lower (they represent larger work)
44
453. **Present Options**
46 - Show top 5 candidates with key details
47 - Include: ID, title, priority, type, age
48 - Ask user to pick or provide different criteria
49
504. **Start Work**
51 - Mark selected bead as in_progress
52 - Show full bead details
53 - Suggest first steps if description includes them
54
55## Examples
56
57```bash
58# Show ready work ranked by suitability
59/next
60
61# Auto-pick and start the next most suitable task
62/next task
63
64# Auto-pick an easy win (quick task)
65/next quick
66
67# Start a specific bead
68/next gauge-abc
69```
70
71## Output Format
72
73```
74## Ready to Work (5 of 12 open)
75
76| # | ID | Pri | Type | Parent/Subs | Title |
77|---|-----------|-----|---------|-------------|--------------------------------|
78| 1 | gauge-abc | P1 | bug | - | Fix login timeout issue |
79| 2 | gauge-def | P2 | feature | 3 subtasks | Add export to CSV |
80| 3 | gauge-ghi | P2 | task | gauge-def | Update dependencies |
81| 4 | gauge-jkl | P3 | feature | - | Dark mode toggle |
82| 5 | gauge-mno | P3 | task | 2 subtasks | Refactor auth service |
83
84Currently in progress: gauge-xyz "Implement caching layer"
85
86Which would you like to work on? (1-5, or specify ID, or "task" to auto-pick)
87```
88
89## Implementation
90
91When invoked:
92
931. Check for current open, not in-progress elsewhere, work:
94 ```bash
95 bd list --status=open
96 ```
97
982. Get ready (unblocked) beads:
99 ```bash
100 bd ready
101 ```
102
1033. Parse command argument:
104 - (none): Show ranked list, ask user to pick
105 - `task`: Auto-select top-ranked bead and start it
106 - `quick`: Auto-select an easy win task and start it
107 - `<bead-id>`: Start that specific bead
108
1094. If specific bead ID provided:
110 ```bash
111 bd show <id>
112 bd update <id> --status=in_progress
113 ```
114
1155. Otherwise, present top 5 options and ask user to choose
116
1176. On selection:
118 - Mark as in_progress
119 - Show full details with `bd show`
120 - If bead has description with steps, highlight first step
121
122## Handling Edge Cases
123
124- **No ready beads**: Show blocked beads and what's blocking them
125- **All in progress**: Warn about context switching, show current work
126- **Invalid ID**: Show error and list valid options
127- **User says "skip"**: Show next 5 options
128
129## Priority Ranking Algorithm
130
131Rank ready beads in this order (first match wins):
132
133| Rank | Criteria |
134|------|---------------------------------|
135| 1 | Any P0 issue (any type) |
136| 2 | P1 bug |
137| 3 | P2 bug |
138| 4 | P1 feature or task |
139| 5 | P1 epic |
140| 6 | P2 feature or task |
141| 7 | P3 bug, feature, or task |
142| 8 | P2 epic |
143| 9 | P3 epic |
144| 10 | Any other non-P4 issue |
145
146**Note**: P4 items are backlog and not shown by default.
147
148## Quick Task Heuristics
149
150When `/next quick` is used, prefer:
1511. Type: task > bug > feature (tasks are usually smaller)
1522. Priority: P3 > P2 > P1 (lower priority = less complex)
1533. Exclude epics (too large for quick wins)
1544. Title keywords: "fix", "update", "add" > "implement", "refactor", "redesign"