beads

Persist tasks and dependencies in a git-backed store for cross-session coordination.

Updated Nov 22, 2025
One-click install
npx skills add https://github.com/Khamel83/oneshot --skill beads-khamel83
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: beads
Source: https://github.com/Khamel83/oneshot/tree/main/archive/v9/skills/beads
Command: npx skills add https://github.com/Khamel83/oneshot --skill beads-khamel83

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Beads solves the challenge of remembering and coordinating tasks across sessions by persisting tasks and their dependencies in a git-backed store, enabling seamless cross-session work and clear handoffs.

Core Features & Use Cases

  • Git-backed persistence of tasks and their dependencies
  • Dependency graphs, blockers, and cross-session coordination
  • Multi-agent coordination and ready-task discovery for uninterrupted progress
  • Handoff-friendly state retention and sync prompts to avoid lost context

Quick Start

Initialize beads in your project, create a first persistent task, and run a sync to persist state.

Frequently Asked Questions about beads

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

FAQPage Schema
How do I persist tasks and dependencies across sessions in git?

You can persist tasks and dependencies across sessions by using a git-backed store that tracks state and links blockers. This enables cross-session work and reliable handoffs by maintaining a single source of truth.

What is the best way to coordinate multi-agent tasks with dependency graphs?

Multi-agent task coordination with dependency graphs is best handled by persisting tasks in git to track blockers and sync state. This allows agents to discover unblocked work and maintain uninterrupted progress without lost context.

Can I use git-backed task tracking for cross-session handoffs?

Yes, git-backed task tracking supports cross-session handoffs by retaining state and prompting syncs to avoid lost context. It ensures reliable work handoffs for complex projects across different sessions.

Do I need specific tooling to track persistent tasks in my project?

Yes, tracking persistent tasks with linked dependencies requires specific beads tooling initialized in your project. You must initialize the tool, create tasks, and run syncs to persist the state in git.

How do dependency blockers work in persistent task tracking?

Dependency blockers in persistent task tracking work by linking tasks in a graph structure within a git-backed store. This allows you to identify blocked tasks and discover ready tasks for continuous progress.

When should I use git-backed persistent task tracking over standard task managers?

You should use git-backed persistent task tracking when you need cross-session coordination, multi-agent collaboration, and reliable handoffs for complex projects. It ensures a single source of truth by syncing state directly in git.