beads-workflow

Name: beads-workflow
Availability: InStock
Author: bennybennison

Manage persistent tasks with dependencies in Dolt-backed projects using Beads.

Updated Apr 11, 2026

Search Tags:#workflow #beads #task-tracking #dependency-management #persistent #dolt

Ready to run

npx skills add https://github.com/bennybennison/agent-toolkit --skill beads-workflow-bennybennison

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: beads-workflow
Source: https://github.com/bennybennison/agent-toolkit/tree/main/skills/beads-workflow
Command: npx skills add https://github.com/bennybennison/agent-toolkit --skill beads-workflow-bennybennison

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Managing tasks that need to persist across session boundaries, survive compaction, and be handed off between multiple agents is difficult without a reliable, version‑controlled system.

Core Features & Use Cases

Persistent task storage using a Dolt database, keeping history, priorities, dependencies, and audit trails.
Commands to create, claim, update, and close tasks atomically, supporting multi‑step plans and multi‑agent pipelines.
Integration hooks for /plan and /orchestrate to turn plans into tracked tasks and coordinate agents.
Automatic handling of sandbox failures by retrying outside the sandbox and distinguishing Beads availability issues.

Quick Start

Initialize Beads in the project, then ask the assistant to list the next ready task to begin work.

Frequently Asked Questions about beads-workflow

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

FAQPage Schema

How do I persist tasks across session boundaries and compaction?▼

Persistent task tracking stores history, priorities, and dependencies in a Dolt database using Beads to survive session boundaries and compaction. This ensures task state survives context loss without relying on volatile session memory.

How do I manage multi-agent task handoffs with dependency tracking?▼

Multi-agent task handoffs use Beads commands to create, claim, update, and close tasks atomically with dependency tracking in a Dolt database. Agents coordinate by picking up ready tasks sequentially based on dependency resolution.

Do I need to initialize a Dolt database before using Beads for task management?▼

Yes, using Beads for task management requires an initialized .beads Dolt database and the bd command-line tool installed. These provide the version-controlled storage layer required for atomic task operations and audit trails.

Can I integrate task tracking with plan generation and orchestration hooks?▼

Yes, Beads integrates with /plan and /orchestrate hooks to turn generated plans into tracked tasks and coordinate agents. This allows multi-step plans to automatically become persistent work items with dependency tracking.

What happens when Beads encounters sandbox failures during task operations?▼

Beads automatically handles sandbox failures by retrying operations outside the sandbox and distinguishing Beads availability issues. This ensures transient sandbox errors do not corrupt atomic task updates or dependency tracking.