bd-issue-tracking

Track multi-session work with beads to preserve context across compaction cycles.

3|Updated Oct 20, 2025
One-click install
npx skills add https://github.com/kenklabnik/chess --skill bd-issue-tracking-kenklabnik
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bd-issue-tracking
Source: https://github.com/kenklabnik/chess/tree/main/docs/claude-code-skill
Command: npx skills add https://github.com/kenklabnik/chess --skill bd-issue-tracking-kenklabnik

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill enables Claude to orchestrate long-running, multi-session work by using beads (bd) to persist context, relationships, and decisions across compaction cycles. It guides how to choose between long-term tracking and lightweight execution, and how to structure work using dependency graphs and issue lifecycles.

Core Features & Use Cases

  • Proactive discovery and issue creation: Capture new work during implementation and link it back to current tasks with discovered-from.
  • Persistent context across sessions: Use the beads database to preserve memory, decisions, and dependencies beyond a single session.
  • Dependency-driven planning: Create blocks, related, parent-child, and discovered-from relationships to model complex workflows and unblock work automatically.
  • Integration with TodoWrite: Complement long-term planning with short-term, visible execution steps.

Quick Start

  • Ensure a .beads/ directory exists in the project or a global beads database is available.
  • Start a session and surface ready work: bd ready --json
  • Create an epic and link child tasks to illustrate multi-session planning:
    • bd create "Implement user authentication" -t epic -d "OAuth integration"
    • bd create "Set up credentials" -t task
    • bd dep add oauth-epic oauth-credentials --type parent-child
    • bd ready --json to see what can begin now

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 multi-session work and preserve context across compaction cycles?

Proactive issue discovery captures new work during implementation and links it back to current tasks with a discovered-from relationship. This creates a persistent dependency graph that survives session restarts and compaction.

How do I set up a beads database for multi-session issue tracking?

Persistent context across sessions is maintained by storing memory, decisions, and dependencies in the beads database. This allows long-running work to resume seamlessly after restarts or compaction cycles without losing project state.

Can I integrate beads issue tracking with TodoWrite for task execution?

Long-term tracking with beads is suited for complex projects with dependencies, side quests, and knowledge work requiring persistent context. Lightweight execution via TodoWrite handles short-term, visible execution steps within a single session.

What is the best way to model dependency graphs for complex project workflows?

Modeling dependency graphs is best done by creating blocks, related, parent-child, and discovered-from relationships between issues. This structures complex workflows and automatically unblocks work as dependencies resolve across sessions.