bd-issue-tracking

Track and persist multi-session work and dependency graphs via the bd CLI.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/blueplane-ai/bp-telemetry-core --skill bd-issue-tracking-blueplane-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bd-issue-tracking
Source: https://github.com/blueplane-ai/bp-telemetry-core/tree/main/.claude/skills/beads
Command: npx skills add https://github.com/blueplane-ai/bp-telemetry-core --skill bd-issue-tracking-blueplane-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Preserves and structures context for multi-session work so AI-assisted development does not lose progress when conversation history is compacted. Enables agents to persist decisions, progress, and next steps in a git-backed issue database instead of ephemeral chat todos.

Core Features & Use Cases

  • Session start ready checks and summaries to surface immediately actionable work.
  • Compaction-survival notes format (COMPLETED / IN_PROGRESS / NEXT / BLOCKERS) for reliable handoffs between sessions.
  • Dependency graph management (blocks, parent-child, related, discovered-from) and JSON output for programmatic parsing.
  • Integration pattern with ephemeral TodoWrite lists for visible in-chat execution while bd preserves long-term context.
  • Use cases: resuming multi-day feature work, capturing side-quests discovered during implementation, planning epics with ordered subtasks.

Quick Start

Ask Claude to run bd ready --json at session start and report available issues, their notes summaries, and suggested next steps.

Frequently Asked Questions about bd-issue-tracking

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

FAQPage Schema
How do I keep AI development context when conversation compaction erases session history?

Multi-session work context survives compaction by persisting decisions, progress, and next steps in a git-backed issue database, replacing ephemeral chat todos with structured compaction-survival notes formatted as COMPLETED, IN_PROGRESS, NEXT, and BLOCKERS.

What is the best way to resume multi-day feature development across multiple AI agent sessions?

Resuming multi-day feature work uses a command-line interface to run a ready check at session start, surfacing available issues, notes summaries, and suggested next steps so agents immediately pick up actionable tasks.

Can I manage dependency graphs for software development tasks using a command-line tool?

Dependency graph management supports blocks, parent-child, related, and discovered-from relationships through command-line operations, outputting JSON structured data for programmatic parsing and integration into automated agent workflows.

How do temporary in-chat todo lists integrate with long-term issue tracking?

Ephemeral in-chat todo lists handle visible execution during a session while a git-backed issue database preserves long-term context, creating an integration pattern where short-term tasks map to persistent multi-session work items.

Does this issue tracking approach require a specific database setup?

The system requires database auto-discovery to locate the git-backed issue database automatically, meaning no manual database configuration is needed as long as the command-line interface has access to the working repository context.

When do I need structured handoff notes for AI-assisted development?

Structured handoff notes are needed when conversation compaction or token limits erase session context during multi-session software development, research, or exploratory agent workflows where losing prior decisions would block progress.