OpenParable
Skip to content
← Back to skills

Bd Issue Tracking

Productivity
bd-issue-tracking

Bd Issue Tracking is an Agent Skill for productivity published in the majiayu000/claude-skill-registry repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Track and manage work with bd issue tracker for persistent context across sessions and compaction events. Use for work needing dependencies, recovery after compaction, or multi-session tracking.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/majiayu000/claude-skill-registry/blob/HEAD/skills/devops/bd-issue-tracking-abatilo-vimrc/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/bd-issue-tracking, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

bd Issue Tracking

bd is a graph-based issue tracker providing persistent memory across sessions. Use for multi-session work; use TodoWrite for simple single-session tasks.

When to Use bd vs TodoWrite

Use bdUse TodoWrite
Multi-session work (days/weeks)Single-session tasks (this hour)
Complex dependencies/blockersLinear step-by-step execution
Need context after compactionAll context in conversation
Fuzzy/exploratory workSimple checklist

Decision rule: "If I need this context in 2 weeks after compaction, use bd"

Session Start

bd ready --json                              # Find available work
bd list --status in_progress --json          # Check active work
bd show <issue-id>                           # Read notes from previous session

Report to user: "X items ready. Issue Y in_progress: [summary from notes]"

Core Operations

# Create issue
bd create "Title" -d "Description" -p 2 -t task --json

# Start work
bd update bd-xxx --status in_progress --json

# Checkpoint progress (at 70% tokens, milestones, blockers)
bd update bd-xxx --notes "COMPLETED: ...\nIN_PROGRESS: ...\nNEXT: ..." --json

# Complete work
bd close bd-xxx --reason "What was done and how verified" --json

# Manage dependencies
bd dep add bd-setup bd-impl --type blocks    # A blocks B
bd dep tree bd-xxx                           # View dependency tree

Notes Format

Write for post-compaction recovery (no conversation context):

COMPLETED: Specific deliverables done
KEY DECISION: Important choices with rationale
IN PROGRESS: Current state + immediate next step
BLOCKERS: What's preventing progress
NEXT: What to do when unblocked

Priority Levels

0=critical, 1=high, 2=normal (default), 3=low, 4=backlog

Description Template

bd create --title "$TITLE" --description "$(cat <<'EOF'
# Description
1-4 sentences: what and why.

# Relevant files and snippets
Files identified during discovery with code snippets.

# Additional sources
Repos explored, web searches performed.
EOF
)" --json

Reference Documentation

For detailed guidance, read these files:

TopicReference
bd vs TodoWrite decisionsreferences/BOUNDARIES.md
Complete CLI referencereferences/CLI_REFERENCE.md
Session workflows & checklistsreferences/WORKFLOWS.md
Dependency types & patternsreferences/DEPENDENCIES.md
Issue creation guidancereferences/ISSUE_CREATION.md
Context recovery patternsreferences/RESUMABILITY.md
Static data usagereferences/STATIC_DATA.md