bd-issue-tracking

Multi-session work persists context and decisions by using beads as a memory layer that survives compaction and conversation boundaries. It stores structured notes, design decisions, and workflow state to maintain progress reliably.

Managing long-running task dependencies is best handled by creating, linking, and visualizing tasks to ensure correct execution order across sessions. This dependency-driven planning preserves workflow state and enables structured session handoffs.

Yes, you can use TodoWrite alongside persistent memory for hybrid task management. This blends long-term beads memory for cross-session context with short-term TodoWrite lists for immediate execution tracking.

Resuming work after a session handoff or compaction relies on structured session notes and ready-state management. You can list ready work, select an issue, and update its status to quickly resume interrupted progress.

Yes, you need the bd CLI to track issues and manage ready-states for AI sessions. It satisfies design notes, acceptance criteria, and session notes through command-line operations like listing ready work and updating statuses.