Track complex, multi-session work with dependency graphs using bd (beads) issue tracker.
SkillScore82Maintained
Automatic
◆Project Management pack
Last verified 8/20/2026
What it changes
Passed 15 of 18 test cases with the skill, and 5 of 18 without it.
Without skill27%
With skill82%
Checks it passed that the model alone missed
Specifies running `bd stats`.
Specifies running `bd blocked`.
Creates a new issue using `bd create`.
and 13 more in the full report
13 fixed5 passed either way3 still failing1 broke
Pass-rate lift
+55 pp
Tokens
+259%
Agent turns
0%
Response time
-63%
Model gemini-3.6-flashMeasured 8/20/2026v118 of 22 cases passed with skill · 18 comparable
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 13 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 13
Prompt
We finished implementing feature sprint tasks `feat-101`, `feat-102`, and `feat-103`. How can we close all three issues in a single CLI invocation while recording 'Completed in PR #88'?
What was checked, without and with the skill
Checked
Without skill
With skill
Specifies closing multiple issues simultaneously with `bd close feat-101 feat-102 feat-103`.
Missed
Passed
Includes `--reason "Completed in PR #88"` in the close command.
Missed
Passed
case-16 · gemini-3.6-flash · 8/20/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md639 linessingle file
bd Issue Tracking
Overview
bd is a graph-based issue tracker for persistent memory across sessions. Use for multi-session work with complex dependencies; use TodoWrite for simple single-session tasks.
When to Use bd vs TodoWrite
Use bd when:
Multi-session work - Tasks spanning multiple compaction cycles or days
Complex dependencies - Work with blockers, prerequisites, or hierarchical structure
Knowledge work - Strategic documents, research, or tasks with fuzzy boundaries
Side quests - Exploratory work that might pause the main task
Project memory - Need to resume work after weeks away with full context
Use TodoWrite when:
Single-session tasks - Work that completes within current session
Linear execution - Straightforward step-by-step tasks with no branching
Immediate context - All information already in conversation
Simple tracking - Just need a checklist to show progress
Key insight: If resuming work after 2 weeks would be difficult without bd, use bd. If the work can be picked up from a markdown skim, TodoWrite is sufficient.
Test Yourself: bd or TodoWrite?
Ask these questions to decide:
Choose bd if:
❓ "Will I need this context in 2 weeks?" → Yes = bd
❓ "Could conversation history get compacted?" → Yes = bd
❓ "Does this have blockers/dependencies?" → Yes = bd
❓ "Is this fuzzy/exploratory work?" → Yes = bd
Choose TodoWrite if:
❓ "Will this be done in this session?" → Yes = TodoWrite
❓ "Is this just a task list for me right now?" → Yes = TodoWrite
❓ "Is this linear with no branching?" → Yes = TodoWrite
When in doubt: Use bd. Better to have persistent memory you don't need than to lose context you needed.