beads

Track issues with dependencies in a git-backed tracker.

Updated Oct 13, 2025
One-click install
npx skills add https://github.com/Joehoel/.dotfiles --skill beads-joehoel
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: beads
Source: https://github.com/Joehoel/.dotfiles/tree/main/.config/opencode/skill/beads
Command: npx skills add https://github.com/Joehoel/.dotfiles --skill beads-joehoel

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Beads provides a persistent, git-backed memory to manage multi-session work with dependencies, so conversation context is preserved across compaction and restarts.

Core Features & Use Cases

  • Graph-based issue tracker that survives conversation changes and compaction
  • Git-backed persistence with dependency management and hierarchical relationships
  • Collaboration-friendly workflow with context recovery across sessions and branches
  • Use Case: coordinate long-running research tasks that require cross-team visibility and memory

Quick Start

Initialize or resume a multi-session task with Beads and ensure changes are synced to Git after each session.

Frequently Asked Questions about beads

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

FAQPage Schema
How do I preserve task context across multiple sessions when conversation memory gets compacted?

A git-backed issue tracker preserves task context across multiple sessions by storing dependency relationships and hierarchical issues in a local Git repository, surviving conversation compaction and restarts. You sync changes to Git after each session.

What's the best way to track issues with dependencies across different git branches?

Tracking issues with dependencies across git branches works best with a graph-based issue tracker that syncs to Git, enabling collaboration-friendly workflows and context recovery across sessions and branches.

Do I need a local Git repository to manage multi-session task memory?

Yes, a local Git repository is required to manage multi-session task memory. The system uses Git-backed persistence to store and sync issues with dependency relationships across sessions.

Can I coordinate long-running research tasks that require cross-team visibility using git?

Yes, you can coordinate long-running research tasks using a git-backed issue tracker that provides cross-team visibility and persistent memory, ensuring context is preserved across compaction and restarts.

How does a graph-based issue tracker handle hierarchical task dependencies?

A graph-based issue tracker handles hierarchical task dependencies by storing dependency relationships and parent-child issue links in a local Git repository, preserving the full task graph across session restarts and compaction events.

When should I avoid using a git-backed issue tracker for multi-session work?

You should avoid a git-backed issue tracker when your workflow lacks a local Git repository or when tasks are short-lived single-session activities that do not require persistent cross-session memory or dependency management.