beads-integration

Sync tasks.md with Beads and persist task memory across Claude Code sessions.

24|6|Updated Nov 30, 2025
One-click install
npx skills add https://github.com/jmanhype/speckit --skill beads-integration
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: beads-integration
Source: https://github.com/jmanhype/speckit/tree/main/.claude/skills/beads-integration
Command: npx skills add https://github.com/jmanhype/speckit --skill beads-integration

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Beads provides persistent memory for long-running projects, enabling context continuity across sessions and robust task tracking.

Core Features & Use Cases

  • Persistent memory: Remembers tasks, discoveries, and dependencies between sessions.
  • Bidirectional syncing: Keeps tasks.md in sync with Beads and vice versa.
  • Project continuity: Avoids context loss during Claude Code context expiration.

Quick Start

Use the Beads CLI to prime and manage tasks across sessions, e.g., bd init and bd ready.

Frequently Asked Questions about beads-integration

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

FAQPage Schema
How do I keep project context and tasks persistent across Claude Code sessions?

Persistent task memory across sessions preserves discoveries, dependencies, and progress using Beads-backed storage. This prevents context loss during long-running projects and maintains continuity when Claude Code sessions expire or compact, keeping your project state alive between work intervals.

Can I sync tasks between a local tasks.md file and a persistent memory system?

Bidirectional syncing keeps tasks.md synchronized with Beads, ensuring your local task file and persistent memory stay consistent. Changes in either direction propagate automatically, eliminating manual reconciliation and keeping spec and plan data aligned across storage layers.

How do I manage multi-session project work without losing context between Claude Code invocations?

Automatic invocation at SessionStart and PreCompact ensures memory persists transparently. The Skill handles context preservation and task synchronization automatically, so you resume work with full project history intact without manual setup between sessions.

What's the best way to track tasks and dependencies across a long-running project?

Task tracking integrates spec and plan data into Beads epics and tasks, mapping your project structure into persistent storage. This provides robust tracking of dependencies and enables project continuity, so no discoveries or decisions are lost as work spans multiple sessions.

Do I need additional setup beyond Beads CLI commands to enable persistent project memory?

The Skill uses Beads CLI commands like bd init and bd ready to prime and manage tasks. No additional infrastructure is required; the Beads integration handles automatic memory persistence and syncing, requiring only standard CLI invocation to activate session-aware memory.