bd-issue-tracking

Track complex project tasks with dependencies across multiple sessions by using a Git-backed issue tracking system. It maintains persistent context and dependency graphs, ensuring work is resumed seamlessly after long breaks or system compactions without losing critical information.

Persistent context survives AI model compactions by storing issues and dependency graphs in a Git-backed issue tracking system. This ensures that all context, decisions, and progress are preserved externally, allowing multi-session work to be resumed accurately.

Yes, you need the bd CLI to manage dependency graphs and epic planning. The issue tracking system requires the bd CLI for operations, which handles proactive issue creation, status maintenance, and side quest handling.

The best way to handle side quests in software engineering workflows is to track them within a Git-backed issue tracking system. It manages side quest handling alongside epic planning and dependency graphs, maintaining persistent context for complex work.

You can resume long-spanning software project work after extended breaks without losing progress by using a Git-backed issue tracking system. It facilitates smooth session handoffs with detailed notes and preserves all context, decisions, and dependency relationships.

You need a dependency graph for issue tracking when managing complex, multi-session work where tasks require input from multiple team members. It automatically surfaces ready work and manages complex relationships between tasks spanning weeks.