bd-issue-tracking

Track multi-session work using beads to model issues and dependencies.

Updated Jan 18, 2026
One-click install
npx skills add https://github.com/anhkhoa2174/cosmo-agents-sdk --skill bd-issue-tracking-anhkhoa2174
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bd-issue-tracking
Source: https://github.com/anhkhoa2174/cosmo-agents-sdk/tree/main/.claude/skills/bd-issue-tracking
Command: npx skills add https://github.com/anhkhoa2174/cosmo-agents-sdk --skill bd-issue-tracking-anhkhoa2174

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

The BD issue-tracking skill provides a persistent memory model for managing complex, multi-session work by using beads (bd) to create issues, dependencies, and notes that survive compaction and session boundaries. It helps teams avoid losing context when conversations end, sessions are paused, or long-running work spans days or weeks.

Core Features & Use Cases

  • Proactive discovery: capture new work and link it to ongoing tasks with discovered-from dependencies.
  • Dependency graph: model blockers, related work, epic/subtask relationships, and provenance to organize work.
  • Session start and handoff: read notes to resume work across sessions and ensure smooth handoffs.
  • Beads memory vs TodoWrite: combine long-term persistence with short-term task visibility.
  • Robust recovery after compaction: reconstruct context from the beads notes and dependencies.

Quick Start

Start by enabling a session: ensure your project has a .beads directory, run bd ready to reveal work, pick an issue and set its status to in_progress, then begin working while beads capture your decisions. You can also create new discovered-from issues during exploration and let the system automatically unblock follow-on work.

Frequently Asked Questions about bd-issue-tracking

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I track complex multi-session work across compaction events?

Multi-session work tracking across compaction events requires a persistent memory model using beads to create issues and dependencies that survive session boundaries. This approach reconstructs context from structured notes to maintain project continuity.

What is the best way to manage a dependency graph for parallel tasks and blockers?

A dependency graph for parallel tasks and blockers is managed by modeling issues with beads to link related work, epic/subtask relationships, and discovered-from provenance. This organizes complex project workflows deterministically.

How do I resume work and read notes for a smooth session handoff?

To resume work for a smooth session handoff, run the beads ready command to reveal available work, read persistent notes from previous sessions, and set an issue status to in_progress before continuing.

Should I use beads memory or TodoWrite for long-term persistent issue tracking?

For long-term persistent issue tracking, beads memory provides the necessary persistence across compaction events, while TodoWrite offers short-term task visibility. Combining both ensures robust recovery and immediate workflow visibility.

Do I need a specific directory setup to enable a deterministic session workflow?

Yes, enabling a deterministic session workflow requires initializing a .beads directory in your project. This setup allows the beads CLI to manage structured notes and track dependencies effectively across sessions.

Can I automatically unblock follow-on work after discovering new issues?

Automatically unblocking follow-on work is supported by creating new discovered-from issues during exploration. This links new tasks to ongoing work and lets the system automatically manage blockers as dependencies resolve.