agentleFS
Sign inStart free
atgreenatgreen/cl-tuition/.agents/skills/beads/SKILL.md

beads

Skill149 starsChanged 2 months agoMITView on GitHub

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.

We split this skill into the rules it gives an agent

10 rules. 0 are common, 6 are distinctive, and 4 are very specific to this project.

  • 0

    Common

    Most of the 11 edited versions we read keep these.

  • 6

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use Beads as the shared project task system.

    line 8
  2. Distinctive:

    If that prints nothing, check whether the repository has an active Beads workspace:

    line 18
  3. Very specific:

    Use the bd CLI when shell access is available.

    line 26
  4. Distinctive:

    Create durable follow-up work when implementation reveals new tasks:

    line 50
  5. Distinctive:

    Use agent-local planning tools only for the current turn's execution checklist.

    line 72
  6. Distinctive:

    Do not create markdown TODO files as the source of truth when Beads is available.

    line 76
  7. Very specific:

    Do not use bd edit; it opens an interactive editor.

    line 77
  8. Very specific:

    Prefer --json when parsing bd output programmatically.

    line 78
  9. Very specific:

    If hooks are installed, bd prime may already be injected.

    line 79
  10. Distinctive:

    Do not auto-close or mutate tasks unless the work is actually complete.

    line 80

“Common” is measured: kept by at least 6 in 10 of the 11 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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:

bd prime

If that prints nothing, check whether the repository has an active Beads workspace:

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:
bd ready
bd list --status=open
bd list --status=in_progress
  1. Inspect before editing:
bd show <id>
  1. Claim work atomically:
bd update <id> --claim
  1. Create durable follow-up work when implementation reveals new tasks:
bd create "Short title" --description="Why this exists and what needs to be done" --type=task --priority=2
  1. Close completed work:
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.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free