beads

Track issues with git-backed persistence and dependency relationships.

10|2|Updated Dec 21, 2025
One-click install
npx skills add https://github.com/lambdamechanic/tooltest --skill beads-lambdamechanic
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: beads
Source: https://github.com/lambdamechanic/tooltest/tree/main/skills/beads
Command: npx skills add https://github.com/lambdamechanic/tooltest --skill beads-lambdamechanic

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Beads provides persistent, git-backed issue tracking to coordinate multi-session work and preserve context across conversation compaction.

Core Features & Use Cases

  • Graph-based dependency management (blocks, related, parent-child, discovered-from) to surface ready work and show relationships.
  • Git-backed persistence across sessions, enabling resume after long gaps and robust auditing.
  • Cross-skill workflows and templates using standard Beads patterns to coordinate multi-tool efforts.

Quick Start

  • Install beads in your project and start a session with the beads daemon.
  • Run bd ready to see what work is available, then begin working and rely on the notes field for compaction survival.

Frequently Asked Questions about beads

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

FAQPage Schema
How do I preserve context for AI agents across conversation compaction?

To preserve context across conversation compaction, use a git-backed issue tracking system that stores persistent notes and dependencies, allowing AI agents to resume multi-session work after long breaks.

What is the best way to manage dependencies and blockers for multi-session work?

Managing dependencies and blockers for multi-session work requires a graph-based issue tracker that surfaces ready tasks and maps relationships like blocks, parent-child, and discovered-from links.

How do I track issue history and audit progress directly in a git repository?

You can track issue history and audit progress directly in a git repository by using a git-backed issue tracker that commits structured task data, preserving an auditable history of all changes.

Can I use standard issue tracking patterns to coordinate cross-skill workflows?

Yes, you can coordinate cross-skill workflows by applying standard issue tracking patterns and templates that guide multiple AI tools through a unified, dependency-aware project graph.

How do I discover what work is ready to start after a long development break?

To discover ready work after a long break, run a command like `bd ready` in your git-backed issue tracker to query the dependency graph and surface tasks with cleared blockers.