Beads
Use for authorized Lotti maintainer work that needs private durable task tracking, issue dependencies, blocker management, multi-session handoff, or shared agent memory. Public contributors use GitHub Issues instead.
Get the complete skill folder, including its scripts and reference files.
When to use this skill
Use Beads when an AI agent needs a reusable SKILL.md workflow for this job: Use for authorized Lotti maintainer work that needs private durable task tracking, issue dependencies, blocker management, multi-session handoff, or shared agent memory. Public contributors use GitHub Issues instead.
When not to use it
Skip Beads when the task is outside the productivity category, or when a more specific skill in this directory already covers the same workflow with clearer triggers.
How to install
Where will you use it?
mkdir -p ~/.claude/skills/beads # Save SKILL.md to ~/.claude/skills/beads/SKILL.md
- Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/beads/SKILL.md. For a shared project, commit the folder at .claude/skills/beads/ instead.
- Current Claude Code detects SKILL.md changes in watched directories during the session. If you just created a top-level skills directory, run /reload-skills. Check that the skill is listed before testing its trigger.
- For Claude chat or Cowork in the Desktop app, manage uploaded skills in Customize > Skills; copying files into a local Claude Code folder is not a Desktop install. Other agents may use different install locations.
Full install guide for Claude, Cursor, and Codex →
Try a starter prompt
After installing the skill, paste this starter prompt into your agent to verify it triggers on a small task.
Use the Beads skill for this task: Use Beads when this documented workflow matches the task. Confirm any required inputs or files before making changes.
What supports this recommendation?
70/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.
- Documentation
- 77/100
- Practical detail
- 68/100
- Source evidence
- 63/100
- Source signals
- 70/100
Model compatibility evidence
- claudeinferred
The skill text mentions Claude or a closely associated term. This is keyword-derived compatibility; no hands-on model test is recorded.
- chatgptuntested
No model-specific signal or recorded compatibility test was found.
- geminiuntested
No model-specific signal or recorded compatibility test was found.
- copilotuntested
No model-specific signal or recorded compatibility test was found.
- llamauntested
No model-specific signal or recorded compatibility test was found.
- perplexityuntested
No model-specific signal or recorded compatibility test was found.
- mistraluntested
No model-specific signal or recorded compatibility test was found.
- grokuntested
No model-specific signal or recorded compatibility test was found.
Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.
What this skill does
# Beads
Use Beads as the private durable task system for authorized Lotti maintainers. Public bugs, feature requests, and contributor coordination stay in GitHub Issues. Local plans remain useful for the current turn.
## First Step
First confirm that the private tracker is available:
```bash bd --readonly list --json ```
If no database exists and the current user is an authorized maintainer, run:
```bash chmod 700 .beads git config beads.role maintainer bd bootstrap ```
If access is denied, do not initialize a competing database. Use GitHub Issues and PR discussion instead.
Run `bd prime` manually when workflow context is needed. Do not install Git, Codex, or Claude hooks for Beads in this repository.
## Core CLI Workflow
1. Pull and find work:
```bash bd dolt pull bd ready bd list --status=open bd list --status=in_progress ```
2. Inspect before editing:
```bash bd show <id> ```
3. Claim work atomically:
```bash bd update <id> --claim ```
4. Create durable follow-up work when implementation reveals new tasks:
```bash bd create "Short title" --description="Why this exists and what needs to be done" --type=task --priority=2 ```
5. Close completed work:
```bash bd close <id> --reason="Completed" ```
6. With explicit authority, publish durable changes:
```bash bd dolt push ```
## What Belongs In Beads
Maintainers use Beads for:
- shared project tasks - blockers and dependencies - discovered follow-up work - work that must survive thread reset, compaction, or handoff - status that another person or agent should be able to resume
Public-facing context must still be copied into GitHub issues, PR descriptions, or review discussion so contributors never need private tracker access.
## Rules
- Do not use `bd edit`; it opens an interactive editor. Use `bd update` flags instead. - Prefer `--json` when parsing `bd` output programmatically. - Do not auto-close or mutate tasks unless the work is actually complete. - Do not store credentials, private user data, or other secrets in Beads. - Do not commit, push Git, or sync Dolt without explicit authority.
Intended uses
- Use Beads when this documented workflow matches the task.
Implementation notes
- Review the source instructions and adapt inputs before running the workflow.
Try it, then tell us how it went
A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.