bd-issue-tracking

Track complex project dependencies across multiple sessions using a persistent, graph-based issue tracker that models blockers, side quests, and parent-child relations to maintain work state. It preserves context and decisions so you can resume work without losing critical information after breaks.

Preserve context for long-running work cycles by storing concise handoffs in issue notes, including completed steps and next actions. This captures design notes and acceptance criteria to maintain a resumable state across compaction cycles.

Model blockers and dependencies by linking issues with specific relation types like blocks and discovered-from. This manages ready state and side quests by mapping out what prevents tasks from proceeding within the dependency graph.

Decompose complex work by creating epics and tasks with parent-child relations to break down large efforts. This hierarchical structure allows you to manage individual components while tracking overall progress within the persistent tracking system.

Multi-session issue tracking works without external dependencies by initializing a local directory and database to store the graph state. This self-contained approach ensures persistent memory for work cycles without requiring additional software or services.

Store handoff notes when ending a work session by updating the issue with a concise summary of completed actions and next steps. This preserves the critical context needed to resume work efficiently in the next session.