BD Issue Tracking FAQs

Question 1

How do I know if my notes are sufficient for a 'compaction' event?

Accepted Answer

Follow the 'Future-me test': ensure notes clearly state what was completed, what is currently in progress, any blockers, and the specific next steps required to resume without asking questions.

Question 2

Does this skill work in the Claude web environment?

Accepted Answer

Yes, while MCP tools are preferred for local environments, bd includes a CLI fallback pattern (e.g., 'bd ready --json') specifically for use in web-based Claude Code sessions.

Question 3

Does bd require manual database setup?

Accepted Answer

No, bd automatically looks for a .beads directory in your current project; if none is found, it defaults to a global database at ~/.beads/default.db.

Question 4

When should I use bd instead of TodoWrite?

Accepted Answer

Use bd for multi-session work with complex dependencies or tasks that need to survive conversation compaction. Use TodoWrite for simple, linear, single-session tasks that will be completed immediately.

Question 5

How does bd survive conversation compaction events?

Accepted Answer

bd stores all issue data, notes, and dependencies in a local or global database file rather than the conversation history, allowing Claude to reconstruct the full context even after history is purged.

BD Issue Tracking

Key Features

Use Cases

BD Issue Tracking

Key Features

Use Cases