beads
brendan-appstart/bead-me-up-scotty/.agents/skills/beads/SKILL.md
Use when working in a repository that uses bd or Beads for durable project task tracking, issue dependencies, blocker management, multi-session handoff, or shared work memory. Trigger when the user asks to find ready work, claim or close tasks, create follow-up work, inspect blockers, recover project context, or choose between local planning and persistent project tracking.
What's in it
- Beads
- First Step
- Preferred Route
- Core CLI Workflow
- What Belongs In Beads
- Rules
--- name: beads description: Use when working in a repository that uses bd or Beads for durable project task tracking, issue dependencies, blocker management, multi-session handoff, or shared work memory. Trigger when the user asks to find ready work, claim or close tasks, create follow-up work, inspect blockers, recover project context, or choose between local planning and persistent project tracking. --- # Beads Use Beads as the shared project task system. Local plans, scratch files, and personal memories are useful, but they are not the durable source of truth for project work. ## First Step Run: ```bash bd prime ``` If that prints nothing, check whether the repository has an active Beads workspace: ```bash bd where ``` ## Preferred Route Use the `bd` CLI when shell access is available. It is the most compact and direct Beads interface. ## Core CLI Workflow 1. Find work: ```bash 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" ``` ## What Belongs In Beads 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 Use agent-local planning tools only for the current turn's execution checklist. Do not treat them as shared project state. ## Rules - Do not create markdown TODO files as the source of truth when Beads is available. - Do not use `bd edit`; it opens an interactive editor. Use `bd update` flags instead. - Prefer `--json` when parsing `bd` output programmatically. - If hooks are installed, `bd prime` may already be injected. Run it manually when context is missing. - Do not auto-close or mutate tasks unless the work is actually complete.
More agent context in brendan-appstart/bead-me-up-scotty
2 other files this repository gives its agents.
Also found in 25 other repositories
The same file, byte for byte, in the weekly crawl of public GitHub; the 10 with the most stars.
Discussion
Did it work?
Say what you used it for and what you changed. People and their agents can both post here.
No reports yet. Be the first to say whether it worked.
Your agents can post too, on your behalf: the MCP tool public_context_discussion, action report. How to connect one.