beads

Persist cross-session project memory using graph-based dependency models.

3|Updated Jan 14, 2026
One-click install
npx skills add https://github.com/spm1001/claude-suite --skill beads-spm1001
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: beads
Source: https://github.com/spm1001/claude-suite/tree/main/skills/beads
Command: npx skills add https://github.com/spm1001/claude-suite --skill beads-spm1001

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

The Beads skill provides persistent, cross-session memory for complex, multi-day work by modeling tasks with dependency graphs and session handoffs. It ensures context survives conversation resets and supports long-running projects across repos.

Core Features & Use Cases

  • Persistent memory across sessions: capture decisions, blockers, and next steps to resume work without re-reading prior chats.
  • Dependency graphs & portfolio view: manage blocks, relationships, and epic hierarchies to guide what is ready to work on.
  • Session handoff & compaction resilience: notes serve as the primary memory, enabling resumption after context loss.
  • Cross-project coordination: view and coordinate work across repos with a read-only beads portfolio.

Quick Start

Use the beads skill to start tracking a multi-session task: create an epic with dependencies, add child tasks, and begin a session with in-progress work.

Frequently Asked Questions about beads

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

FAQPage Schema
How do I keep persistent memory across multiple coding sessions for complex projects?

Persistent cross-session memory tracks decisions, blockers, and next steps using a graph-based dependency model, letting you resume multi-week tasks without re-reading prior chats after context resets.

How does session handoff work for long-running tasks with dependency graphs?

Session handoff uses notes as the primary memory source, capturing task dependencies and progress to enable compaction resilience and seamless resumption of multi-day work across conversation resets.

What do I need to set up cross-repo coordination with a dependency graph model?

Cross-repo coordination requires a local Git-backed database and beads tooling via CLI or MCP to persist state, model task dependencies, and view a read-only portfolio across repositories.

Can I manage epic hierarchies and task blocks for multi-week project work?

Yes, you can model epic hierarchies with child tasks, track blockers, and manage dependency relationships to guide which tasks are ready to work on during multi-week project sessions.

What's the best way to resume in-progress work after losing conversation context?

Resume in-progress work by relying on persistent notes stored in a Git-backed database, which captures prior decisions and next steps to rebuild context after compaction or conversation loss.

When should I not use a graph-based session handoff approach for project memory?

Graph-based session handoff is designed for complex, multi-day work with blockers and cross-repo coordination; single-session or simple tasks without dependencies likely do not require this persistent memory overhead.