skills.rest
r0man
r0manCOMMUNITY
Explore all skills by this author →
GitHub

beads

Track multi-session work with a Git-backed dependency graph.

3|1|Updated Jan 29, 2022
Search Tags:#git#beads#compaction#audit-trail#persistent-memory#dependency-graph
One-click install
npx skills add https://github.com/r0man/guix-home --skill beads-r0man
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: beads
Source: https://github.com/r0man/guix-home/tree/main/modules/r0man/guix/home/files/claude-code/skills/beads
Command: npx skills add https://github.com/r0man/guix-home --skill beads-r0man

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires bd, git, jq, and includes references (resource) components.

What problem does it solve?

Beads provides a Git-backed, persistent memory system for AI agents to track complex, multi-session work with dependencies. Context persists across conversation compaction.

Core Features & Use Cases

  • Dependency Graphs: Track blocks, parent-child, discovered-from, and related relationships.
  • Compaction Survival: Notes and decisions survive conversation summarization, enabling resumed work after context reductions.
  • Audit Trails & Versioning: Git-backed issue history in .beads/issues.jsonl for traceability.
  • Smart Discovery: Commands like bd ready and bd blocked surface what to work on next.
  • Cross-Session Memory: Maintains state across sessions and teammates via git.

Quick Start

Create an epic with children, link dependencies, and sync with git to persist across sessions.

Frequently Asked Questions about beads

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

FAQPage Schema
How do I track dependencies and blockers across multiple sessions on a long-running project?▼

Beads provides a Git-backed dependency graph that tracks blocks, parent-child, and related relationships, persisting across sessions. Use commands like `bd ready` and `bd blocked` to surface what to work on next, with state maintained through `.beads/issues.jsonl` audit trails.

Can I keep my project context from being lost when conversation sessions end?▼

Beads maintains persistent memory across session compaction by storing notes and decisions in a Git-backed audit trail. Your work state, dependencies, and metadata survive context reductions, letting you resume from where you left off.

How do I organize epics, blockers, and side quests with metadata like priority and assignees?▼

Create epics with parent-child relationships and attach rich metadata including priority, type, labels, and assignees. Beads stores this structure in Git alongside dependency graphs, making it queryable across sessions.

What's the best way to maintain an audit trail and version history for complex work across a team?▼

Beads uses Git-backed versioning with `.beads/issues.jsonl` storing full issue history for traceability. Cross-session memory shared via Git lets teammates access the same dependency graph and decision log.

Do I need special setup or dependencies to use persistent memory for multi-session AI workflows?▼

Beads requires `bd`, `git`, and `jq` as dependencies. It integrates with your existing Git workflow, syncing automatically to persist state without additional infrastructure.

Related Skills

Explore More Software Engineering Skills→
cameronraysmithcameronraysmith
14

issues-beads-init

Initialize beads issue tracking with dolt database persistence for new repositories.

Community
Intermediate
lambdamechaniclambdamechanic
2

bd-workflow

Manage issue tracking with dependency-aware beads and JSON export.

Official
Basic
bbugyi200bbugyi200
5

sase_changespecs

Query and manage SASE ChangeSpec lifecycle states and metadata via CLI.

Community
Advanced
ReinaMacCredyReinaMacCredy
223

beads

Track multi-session work with dependency graphs and git-backed persistence.

Community
Advanced