beads

Organize work as a hierarchical graph of epics and tasks.

1|Updated Aug 14, 2024
One-click install
npx skills add https://github.com/bresilla/dot --skill beads-bresilla
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: beads
Source: https://github.com/bresilla/dot/tree/main/.config/opencode/skill/beads
Command: npx skills add https://github.com/bresilla/dot --skill beads-bresilla

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Beads acts as an external working memory, preserving context, decisions, and the structure of work across sessions, so you don't lose progress when you restart.

Core Features & Use Cases

  • Hierarchical work graph: manage epics, tasks, and subtasks with clear parent-child relationships.
  • Dependency-aware planning: encode and visualize how work blocks other work, ensuring you always pick ready tasks.
  • Decision logging as context: capture descriptions and comments that travel with tasks to inform future sessions.
  • Deterministic execution workflow: use predefined commands to create, update, and discover work without memory drift.

Quick Start

bd create "New feature" -t epic -p 0 -d "Context for the epic" bd create "UI work" -p 1 --parent beads-epic-id -d "Implement UI" bd comment beads-epic-id "Decisions and constraints"

Frequently Asked Questions about beads

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

FAQPage Schema
How do I track project dependencies and tasks across sessions without losing context?

Track project dependencies and tasks across sessions by organizing work into a persistent hierarchical graph of epics and tasks. This external working memory preserves context, structure, and decisions to prevent progress loss when restarting.

What is the best way to decompose epics into subtasks for product management?

Decompose epics into subtasks for product management by using predefined command-line commands to create hierarchical IDs. This structures parent-child relationships and encodes dependency-aware planning to ensure you always pick ready tasks.

How do I log decisions and constraints directly within my workflow tasks?

Log decisions and constraints within workflow tasks by capturing descriptions and comments that travel with the tasks. This context informs future sessions and prevents memory drift during cross-session planning.

Do I need external software to manage hierarchical task IDs and dependencies?

You do not need external software to manage hierarchical task IDs and dependencies beyond a Beads-compatible workflow. Standard command-line usage handles creation, updates, and discovery of work without memory drift.

How does dependency-aware planning identify which tasks are ready to start?

Dependency-aware planning identifies ready tasks by encoding and visualizing how work blocks other work within the hierarchical graph. This ensures you select tasks that have no unresolved parent dependencies blocking execution.

When should I use a persistent work graph instead of standard task tracking?

Use a persistent work graph instead of standard task tracking for projects benefiting from disciplined work decomposition, dependency tracking, and cross-session decision logs to maintain reliable planning and prevent memory drift.