bd-issue-tracking

Persistent multi-session issue tracking uses beads to preserve context, decisions, and dependency graphs across compaction cycles. This ensures work resumes seamlessly after session boundaries by capturing blockers and complex dependencies that would otherwise be lost.

Managing complex dependency graphs for long-term projects requires tracking relationships like blocks, related, parent-child, and discovered-from. This approach automatically surfaces ready tasks and keeps work organized across extended timeframes with blockers and side quests.

Start a new multi-session project by running the ready command and reviewing the in_progress work to plan your next steps. This workflow provides structured discovery, execution, planning, and handoff across session boundaries.

Yes, hybrid workflows support TodoWrite for short-term execution alongside beads for long-term memory. This integration ensures continuity and auditability by combining immediate task management with persistent context that survives session boundaries.

Persistent issue tracking is not ideal for simple, single-session tasks. It is designed specifically for complex projects spanning days or weeks with blockers, side quests, and memory needs where work must survive compaction cycles and session boundaries.