beads
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.
- License 许可
- MIT
- 最近更新
- 2026-10-17
- Stars
- ★ 1
- Forks
- 0
01 前言 Front Matter
- 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.
02 资源文件 1
- 参考文档agents/openai.yaml175 B
03 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
Commands
The full command conventions (find, read, claim, create with types, labels, and spec linkage, update, dependencies, close, views, session completion, context profiles) live in docs/agents/issue-tracker.md. It is the single source; follow it. Its rules bind here too: never run bd edit, never use bd memory, do not use markdown TODO files as the source of truth, and prefer --json when parsing bd output programmatically.
If hooks are installed, bd prime may already be injected. Run it manually when context is missing.
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. Do not auto-close or mutate tasks unless the work is actually complete.
04 同仓库更多 Skills
writing-for-agents
Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.
wizard
Generate an interactive bash wizard that walks a human through steps only they can perform. Use when provisioning infrastructure, setting up credentials or CI secrets, walking an unfamiliar third-party dashboard, or running a one-off migration or cutover. Don't invoke this for steps the agent can perform itself.
wayfinder
Plan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.
wait-what
Stop. That last message did not land: re-pitch it.
visual-spec
Turn the grilled conversation into a spec, optionally confirming risky decisions as a visual HTML explainer first, then publish it to the issue tracker.
triage
Move issues and external PRs through a state machine of triage roles, categorise, verify, grill if needed, and write agent-ready briefs.