Persist task context across sessions using Git-backed beads.
npx skills add https://github.com/johnnymo87/workstation --skill beads-johnnymo87
Please help me install this Agent Skill. Skill: beads Source: https://github.com/johnnymo87/workstation/tree/main/assets/claude/skills/beads Command: npx skills add https://github.com/johnnymo87/workstation --skill beads-johnnymo87
Beads provides a Git-backed memory system to preserve task context across sessions, ensuring work survives compaction and session boundaries.
To begin, surface ready beads work with the bd ready command, create beads for ongoing tasks using bd create, and update beads notes as decisions and progress occur. Then use bd sync to persist changes.
High-intent search queries and answers about installing and using this skill.
Beads provides Git-backed memory that survives session boundaries and compaction by storing task context as persistent records. Use bd create to capture ongoing work, bd ready to surface actionable tasks, and bd sync to persist changes to Git, ensuring your project state and decisions remain accessible across long sessions.
Yes. Beads supports linking beads with dependency relationships including blocks, discovered-from, parent-child, and related connections. This enables you to map blockers, trace discovery chains, and maintain visibility across interconnected work items throughout complex projects.
Create beads for each decision point or blocker using bd create, update notes as progress occurs with bd update, and sync to Git via bd sync. Beads stores these annotations persistently, making them retrievable for future sessions and handoffs without manual re-entry.
Beads is designed for multi-session knowledge work and long-running initiatives. Surface ready work with bd ready, create beads for new tasks, link them by dependency type, annotate decisions and blockers, then sync—building a persistent, Git-backed record that outlives individual sessions.
Yes. Beads requires Git as its backing store to persist task context across sessions and compaction. Ensure your project is initialized in a Git repository; beads will store memory records there, making them durable and accessible across workspace boundaries.
Beads' Git-backed approach is durable but scales with project complexity. It excels at capturing decisions and blockers for handoffs and long-running work, but manual linking and note discipline are required—automation of inference or conflict resolution across complex dependency graphs is not built in.
cameronraysmithInitialize beads issue tracking with dolt database persistence for new repositories.
anhkhoa2174Track multi-session work using beads to model issues and dependencies.
GGPromptsConvert vague ideas into structured beads workflows with epics and dependencies.
mrfManage persistent task memory for AI coding agents with Beads.
