bd

Manage backlog items by creating, updating, closing, and syncing issues with bd.

Updated Jan 23, 2026
One-click install
npx skills add https://github.com/datorresb/vibecoding-starter --skill bd-datorresb
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bd
Source: https://github.com/datorresb/vibecoding-starter/tree/main/.claude/skills/core/bd
Command: npx skills add https://github.com/datorresb/vibecoding-starter --skill bd-datorresb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill streamlines backlog management by turning every task into a tracked issue using the bd tool, ensuring visibility, traceability, and structured delegation.

Core Features & Use Cases

  • Create issues with bd create and assign to subagents for execution.
  • Update statuses with bd update and monitor progress via bd list or bd ready.
  • Close completed work with bd close and keep git-synced data with bd sync.
  • Use-case: transform a user request into a set of discrete issues and track lifecycle end-to-end.

Quick Start

  • Run bd onboard to get oriented.
  • Run bd ready to see available work.
  • Create an issue with bd create "<title>".
  • Claim work with bd update <id> --status in_progress.
  • Complete work with bd close <id> and bd sync.

Frequently Asked Questions about bd

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

FAQPage Schema
How do I manage agile backlog items and turn tasks into trackable issues?

Backlog management involves turning tasks into trackable issues to ensure visibility, traceability, and structured delegation. You can orchestrate this workflow by using lifecycle commands to create, assign, update, and close issues end-to-end.

How do I create and assign issues for workflow automation in an agile project?

You can create and assign issues for workflow automation by running a creation command with a title, then updating the issue status to in_progress. This allows subagents to claim and execute the discrete issues within the project.

What is the best way to track issue progression and monitor task status in a backlog?

Tracking issue progression and monitoring task status is best handled by listing available work or ready items. You can then update statuses as work moves forward and close completed items to maintain auditability and visibility.

Do I need to run an onboarding command before setting up issue tracking?

Running an onboarding command is required to get oriented with the issue tracking environment. It prepares the workspace so you can immediately start creating, updating, and syncing backlog issues.

How do I keep git-synced data updated after closing backlog issues?

To keep git-synced data updated after closing backlog issues, you run a sync command immediately following the close command. This ensures completed work and issue lifecycle changes maintain traceability with your repository.