skills.rest
abatilo
abatiloCOMMUNITY
Explore all skills by this author →
Website𝕏@aaronbatiloGitHub

bd-issue-tracking

Track multi-session issues with dependency graphs and JSON I/O.

10|2|Updated Sep 28, 2015
Search Tags:#workflow#dependencies#beads#Claude Code#multi-session#bd#issue-tracking
One-click install
npx skills add https://github.com/abatilo/vimrc --skill bd-issue-tracking-abatilo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bd-issue-tracking
Source: https://github.com/abatilo/vimrc/tree/main/skills/bd-issue-tracking
Command: npx skills add https://github.com/abatilo/vimrc --skill bd-issue-tracking-abatilo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a structured approach to tracking long-running work across sessions using bd, a graph-based issue tracker that persists through compaction. It helps teams maintain context, dependencies, and lifecycle of issues.

Core Features & Use Cases

  • Persistent memory across sessions: bd remembers issues, decisions, and blockers even after conversation history is cleared.
  • Dependency graph for complex work: blocks, related, parent-child, discovered-from relationships help manage multi-step efforts.
  • Side quests and resumability: capture side findings and resume work later with full context.
  • Workbench integration: Works with the beads plugin and Claude Code skill for proactive issue management.

Quick Start

Use bd to start a new multi-session task: "Create an epic for API migration" and then "bd ready" to discover ready 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 work across multiple Claude Code sessions without losing context?▼

Multi-session work tracking uses bd, a graph-based issue tracker that persists issues, decisions, and blockers even after conversation history compaction. bd stores dependencies and lifecycle state independently, letting you resume long-running projects with full context restored.

What's the best way to manage dependencies and blockers in complex multi-step projects?▼

bd issue tracking models dependencies as a graph with blocks, related, parent-child, and discovered-from relationships. This dependency graph lets you identify which tasks are ready to work on and unblock downstream work systematically.

How do I resume a long-running project after my conversation is compacted?▼

bd stores issue state, notes, and side quest findings persistently outside conversation history. Use bd ready to discover what work is unblocked and resume with full context, bypassing the need to rebuild project memory after compaction.

Can I use bd issue tracking with the beads plugin and Claude Code workflow?▼

Yes. bd integrates with the beads plugin and Claude Code skill for proactive issue management. CLI-based operations support JSON I/O, letting you query, update, and discover work within your existing Claude Code workflow.

What kinds of relationships does bd support for organizing issues?▼

bd tracks blocks (hard dependencies), related (linked issues), parent-child (hierarchical breakdown), and discovered-from (exploration trails) relationships. These relationship types let you model epics, side findings, and recovery paths across your work graph.

Related Skills

Explore More Software Engineering Skills→
AppsVortexAppsVortex
31

arn-code-ensure-config

Verify and establish Arness Code configuration in CLAUDE.md for projects.

Official
Advanced
zdpkzdpk

openspec-archive-change

Archive completed OpenSpec experimental changes after validation for recoverable history.

Community
Advanced
AveerAveer
1

zeus-beads

Track tasks and dependencies in a git-backed Dolt graph database.

Community
Advanced
ReinaMacCredyReinaMacCredy
223

beads

Track multi-session work with dependency graphs and git-backed persistence.

Community
Advanced