beads

Track persistent multi-session work using bd dependency graphs and structured session notes.

Updated May 10, 2025
One-click install
npx skills add https://github.com/adteco/glapi --skill beads-adteco
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: beads
Source: https://github.com/adteco/glapi/tree/main/.claude/skills/beads
Command: npx skills add https://github.com/adteco/glapi --skill beads-adteco

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill keeps strategic, multi-session work from vanishing when conversation history is compacted by capturing the work state, dependencies, and decisions inside the bd bead database so future sessions can resume with full context.

Core Features & Use Cases

  • Session start and handoff checklists describe how to run bd ready, review in-progress notes, and report summaries so every session begins with shared context.
  • Compaction survival guidance defines rigorous COMPLETED/IN_PROGRESS/BLOCKERS/KEY DECISIONS notes, checkpoint triggers, and issue lifecycle rules to preserve long-horizon knowledge.
  • Issue creation, dependency, and TodoWrite integration playbooks ensure you document blockers, discovered work, and execution steps for knowledge work that spans days or weeks.

Quick Start

Check bd ready to surface available work and describe the context before starting persistent multi-session tasks.

Frequently Asked Questions about beads

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

FAQPage Schema
How do I preserve project context when conversation history is compacted?

To preserve project context during compaction, capture work state, dependencies, and decisions inside a persistent bead database. This ensures future sessions can resume complex multi-session work with full historical context intact.

What is the best way to track dependencies for multi-session knowledge work?

Tracking dependencies for multi-session knowledge work requires managing bead dependency graphs that document blockers, discovered work, and execution steps. This approach maintains project memory beyond single sessions and spans compaction cycles.

How do I handle session handoff for complex tasks that span days or weeks?

Session handoff for long-horizon tasks requires structured checklists defining how to run readiness checks, review in-progress notes, and report summaries. This ensures every session begins with shared context and accurate work state.

Does TodoWrite integration work with multi-session issue tracking?

TodoWrite integration works with multi-session issue tracking by documenting blockers, discovered work, and execution steps within bead dependency graphs. This combination satisfies resumability requirements for knowledge work spanning days or weeks.

When do I need compaction survival guidance for persistent work?

Compaction survival guidance is needed when complex knowledge-work tasks span compaction cycles, involve blockers, or require project memory beyond single sessions. It defines rigorous notes capturing completed work, progress, blockers, and key decisions.