bd-issue-tracking

Track multi-session work with dependency graphs; survives compaction; use when context spans sessions or has complex dependencies.

• Graph-based issue tracker for persistent memory across sessions
• Tracks complex, multi-session tasks with dependencies and blockers
• Preserves work history and context through compaction events
• Uses beads (bd) to store issues, notes, and progress

• Saves work history and context across sessions
• Preserves issues, dependencies, and notes through compaction
• Supports multi-session, complex, and exploratory work
• Auto-discovers project or global database (no config needed)
• Reconstructs context post-compaction via notes field
• Critical: only beads survive compaction; conversation history does not
• Must write clear notes for future recovery
• Always check `bd ready` and `bd list --status in_progress` at session start

1. 1.Check for bd availability at session start
2. 2.Run `bd ready --json` and `bd list --status in_progress --json`
3. 3.Read notes field to understand prior work and blockers
4. 4.Update notes at context low or token >70% thresholds
5. 5.Use `bd blocked --json` if no work is ready
6. 6.Always report context to user with summary and next steps