beads

Track dependency-aware issues with bd commands and JSONL history.

12|1|Updated Jun 4, 2013
One-click install
npx skills add https://github.com/bostonaholic/dotfiles --skill beads-bostonaholic
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: beads
Source: https://github.com/bostonaholic/dotfiles/tree/main/claude/skills/beads
Command: npx skills add https://github.com/bostonaholic/dotfiles --skill beads-bostonaholic

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Beads solves the problem of untracked blockers and unclear dependencies in AI-driven projects by providing structured, dependency-aware issue tracking.

Core Features & Use Cases

  • Dependency-aware issue tracking with blockers and relationships
  • Auto-sync to JSONL (.beads/issues.jsonl) for version control
  • Ready-work discovery and linked issues to surface work quickly
  • AI-friendly commands: bd create, bd update, and bd close to manage task lifecycle

Quick Start

Create a new beads issue titled Review project setup and set it to type task with priority 1.

Frequently Asked Questions about beads

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

FAQPage Schema
How do I track dependencies and blockers in AI-driven project workflows?

You can track dependencies in AI-driven project workflows by using structured issue tracking that maps blockers and relationships. It auto-syncs linked issues to a JSONL history file, ensuring teams discover ready work and maintain version-controlled project states.

How do I create and manage a structured issue using the bd command?

To create a structured issue, use the bd create command to define the title, type, and priority. You can then manage the task lifecycle by updating status with bd update and resolving it with bd close, keeping all changes synced to the JSONL history file.

Can I use JSONL history files for version control in issue tracking?

Yes, you can use JSONL history files for version control in issue tracking. The system automatically exports changes to a .beads/issues.jsonl file, creating a version-controlled record of task states, dependencies, and linked issues for software, research, and design projects.

Does this issue tracking system support multiple collaborators and automatic state syncing?

Yes, this issue tracking system supports multiple collaborators with automatic state syncing. It keeps teams aligned by automatically updating linked issues and discovering ready work across software, research, and design tasks.

What is the best way to discover ready work in a dependency-aware project environment?

The best way to discover ready work is using a structured issue tracker that surfaces tasks with cleared blockers. It automatically identifies linked issues without active dependencies, allowing teams to quickly find and execute available work within the AI workflow.

Are there limitations to using JSONL files for complex dependency management?

JSONL files handle dependency management by appending state changes sequentially, which is ideal for version control but may require parsing for complex queries. The bd commands enforce the workflow, ensuring dependency-aware tracking remains structured across collaborators.