bd-issue-tracking

Track multi-session issues with dependency graphs using beads.

Updated Jun 10, 2025
One-click install
npx skills add https://github.com/Kingly-Agency/kingly-claude-adapter --skill bd-issue-tracking-kingly-agency
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bd-issue-tracking
Source: https://github.com/Kingly-Agency/kingly-claude-adapter/tree/main/plugins/cache/beads-marketplace/beads/0.29.0/examples/claude-code-skill
Command: npx skills add https://github.com/Kingly-Agency/kingly-claude-adapter --skill bd-issue-tracking-kingly-agency

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps Claude use beads to track and manage multi-session work with dependency graphs. It preserves memory across compaction cycles, enabling reliable continuity for long-running projects and knowledge work.

Core Features & Use Cases

  • Proactive issue tracking: Create and link issues for work that spans multiple sessions.
  • Dependency graphs: Model blocks, related, parent-child, and discovered-from relationships to surface blockers and context.
  • Session memory across compaction: Preserve decisions, outcomes, and history so work can resume after gaps.
  • Guidance on when to use beads vs TodoWrite: Decide between long-lived bead issues and single-session checklists.
  • Integration with beads plugin: Works alongside MCP tools for quick operations and persistence.

Quick Start

Ask Claude to start a beads-based workflow for a project: "Let's track this feature with bd across sessions and capture dependencies."

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 work across multiple sessions without losing context during compaction?

Multi-session issue tracking with beads preserves memory across compaction cycles by storing decisions, outcomes, and dependencies as persistent bead issues. Claude resumes work with full context after gaps, enabling reliable continuity for projects spanning days or weeks.

What's the difference between using beads for issue tracking versus a single-session checklist?

Beads are long-lived issues suited for complex, multi-session work with dependencies and blockers. TodoWrite is for single-session checklists. Use beads when work spans multiple sessions and requires proactive dependency graphing and lifecycle management across compaction.

How do I model dependencies and blockers in multi-session workflows?

Dependency graphs in beads track blocks, related, parent-child, and discovered-from relationships. This surfaces blockers and context needed for knowledge-work tasks, enabling Claude to prioritize work and understand how issues connect across complex projects.

When should I start a beads-based workflow instead of manual notes?

Start a beads workflow for knowledge-work tasks spanning days or weeks involving complex dependencies, side quests, and project memory. Beads satisfy session start checks, readiness discovery, and notes-based resumability with explicit dependency relationships preserved across compaction.

Can I use beads with the MCP tools plugin for issue operations?

Yes, beads integrate with the MCP tools plugin for quick operations and persistence. The plugin enables rapid issue creation, linking, and dependency updates while beads handle session memory preservation and compaction survival.