beads

Track multi-session work with dependency graphs using beads issue tracker.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Beads enables tracking of complex, multi-session work with dependency graphs and persistent context across compaction cycles. It is ideal for tasks that span days or weeks and require memory across interruptions; for simple single-session tasks, use TodoWrite.

Core Features & Use Cases

  • Graph-based issue tracker: manage issues, notes, dependencies, and statuses with long-term context.
  • Cross-session continuity: preserves memory across compaction events so you can resume with full context.
  • Dependency awareness: supports blocks, related, parent-child, and discovered-from relationships to model complex work.
  • Surviving compaction: critical notes and history survive compaction, enabling safe post-compaction recovery.
  • Decision journaling: structured notes with completions, in-progress state, blockers, and decisions for future you.

Quick Start

Create a beads issue and populate the notes with a resumable state, e.g.:

  • bd create "Research contract clauses" -p 2
  • bd update <issue-id> --notes "COMPLETED: contract clause shortlist; IN PROGRESS: draft negotiation terms; BLOCKERS: legal review pending; NEXT: lock in final terms" --json After weeks or days, use bd show <issue-id> --json to reconstruct full context.

Frequently Asked Questions about beads

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

FAQPage Schema
How do I track work across multiple sessions with persistent context?

Beads is a graph-based issue tracker that preserves memory across compaction cycles. Create issues with structured notes documenting completed work, in-progress tasks, blockers, and decisions, then use bd show to reconstruct full context after interruptions or days later.

Can I model complex dependencies between tasks and issues?

Yes, beads supports multiple dependency types—blocks, related, parent-child, and discovered-from relationships—enabling you to map intricate work graphs. Use bd dep tree to visualize and navigate dependencies across your tracked issues.

What's the best way to structure notes for work I need to resume later?

Organize notes with explicit sections: COMPLETED (what finished), IN PROGRESS (active work), BLOCKERS (what's stuck), and NEXT (what comes after). This structured format ensures your future self has actionable context when resuming after compaction or long interruptions.

When should I use beads instead of simpler task tools?

Use beads for work spanning days or weeks requiring memory across interruptions, complex dependencies, or knowledge work needing persistent context. For simple single-session tasks, simpler tools are more appropriate.

How does beads survive compaction cycles?

Critical notes and history are explicitly preserved during compaction events. Beads stores bead data—issues, notes, dependencies, status—in a way that survives compaction, enabling safe post-compaction recovery and resumed workflows.