beads

Track durable project tasks, blockers, and handoffs across sessions.

1|Updated Apr 27, 2026
One-click install
npx skills add https://github.com/darkmatter/skills --skill beads-darkmatter
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: beads
Source: https://github.com/darkmatter/skills/tree/main/.agents/skills/beads
Command: npx skills add https://github.com/darkmatter/skills --skill beads-darkmatter

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Beads gives teams a durable source of truth for project work so tasks, blockers, and handoffs do not disappear into chat history or ephemeral notes.

Core Features & Use Cases

  • Ready-work discovery: Find tasks that are available to start right now.
  • Atomic claiming and closure: Claim work, track progress, and close completed items without losing state.
  • Blocker and dependency management: Record follow-up work and relationships that need to survive multi-session collaboration.
  • Use case: A developer returns after context loss, primes the workspace, checks what is ready, claims the next task, and creates durable follow-up work when implementation reveals new steps.

Quick Start

Ask the assistant to prime the Beads workspace, inspect ready tasks, and help you claim the next item to work on.

Frequently Asked Questions about beads

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

FAQPage Schema
How do I track project tasks and blockers across multiple sessions?

Durable task tracking across sessions is managed by priming the Beads workspace, which stores persistent project memory so tasks and blockers survive context loss. You can discover ready-work, claim items, and close them without losing state.

What is the best way to manage work handoffs for shared engineering workflows?

Managing handoffs for shared engineering workflows requires recording follow-up work and dependencies in a durable workspace state. This ensures multi-session collaboration survives without details disappearing into ephemeral notes or chat history.

How do I find available tasks to start working on right now?

Finding ready-work involves inspecting the primed Beads workspace for available tasks. You ask the assistant to check what is ready and help you claim the next item, ensuring work discovery is atomic and consistent.

Do I need the bd CLI to manage persistent project memory?

Yes, the bd CLI is required to manage persistent project memory safely and consistently. The Beads workspace state depends on this CLI to handle repository work discovery, task claiming, and completion tracking.

How does claiming a task work when multiple developers share a repository?

Atomic claiming and closure allows developers to claim work, track progress, and close completed items without losing state. This shared engineering workflow ensures tasks are not duplicated across team members.

Why should I use a durable workspace state instead of chat history for task tracking?

A durable workspace state provides a source of truth so project work, blockers, and handoffs do not disappear into chat history or ephemeral notes. It maintains consistent multi-session collaboration and context recovery.