beads

Track multi-agent task units as beads in a database with JSONL export.

8|1|Updated Jan 21, 2024
One-click install
npx skills add https://github.com/azigler/dotfiles --skill beads-azigler
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: beads
Source: https://github.com/azigler/dotfiles/tree/main/agents/skills/beads
Command: npx skills add https://github.com/azigler/dotfiles --skill beads-azigler

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill solves the problem of keeping complex, multi-agent work organized so the right next action is always clear, with a complete handoff packet tied to code commits.

Core Features & Use Cases

  • One bead per commit: ensures every unit of work is closed before the merge and recorded in commit history via a Bead trailer.
  • Rich bead handoff packets: uses structured fields (description, design, acceptance criteria, notes, deps, external refs) so another agent can pick up cold without guessing.
  • State discovery and triage: supports commands to find what is ready, blocked, stale, or orphaned, and pair with graph-aware triage via bv.

Quick Start

Use the beads skill to create and close one tracked task end-to-end by running: br create -p 2 "task: auth token refresh" then br update <id> --description "..." --acceptance-criteria "..." and finally br close <id> before you commit.

Frequently Asked Questions about beads

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

FAQPage Schema
How do I track multi-agent development tasks with commit-level traceability?

Multi-agent task tracking with commit-level traceability is managed by representing each unit of work as a bead persisted in an agent-friendly SQLite database. Beads are closed before merges and recorded in commit history via a Bead trailer for full traceability.

What is a bead handoff packet for multi-agent workflows?

A bead handoff packet is a structured record containing description, design, acceptance criteria, notes, dependencies, and external references. It allows another agent to pick up a task cold without guessing by providing all required context in a standardized format.

How do I create and close a tracked task end-to-end using CLI operations?

Create a tracked task by running a CLI create command with a priority and title, update its structured fields using an update command, then close it before committing. Closing syncs the SQLite database state to JSONL for version control.

Can I use SQLite and JSONL exports for dependency-aware task triage?

SQLite and JSONL exports support dependency-aware task triage by allowing commands to discover what work is ready, blocked, stale, or orphaned. The JSONL export enables version control integration while the database handles readiness checks across spec, check, test, impl, and eval stages.

Does this task tracking approach work for multi-agent orchestration across spec and test stages?

This task tracking approach is designed specifically for multi-agent orchestration across spec, check, test, impl, and eval stages. It applies dependency-aware readiness checks and structured handoffs so agents can coordinate work transitions without losing context.

What are the limitations of file-based task tracking for multi-agent development?

File-based task tracking without a database can lose dependency-aware readiness state and make triage across multiple agents difficult. This Skill addresses those limitations by persisting bead state in SQLite and syncing to JSONL for version control compatibility.