← ClaudeAtlas

bd-issue-trackinglisted

Track complex, multi-session work with dependency graphs using bd (beads) issue tracker. Use when work spans multiple sessions, has complex dependencies, or requires persistent context across compaction cycles. For simple single-session linear tasks, TodoWrite remains appropriate.
Microck/ordinary-claude-skills · ★ 394 · AI & Automation · score 79
Install: claude install-skill Microck/ordinary-claude-skills
# 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?" → Ye