tasks
Work on or manage records in BB Tasks, including task keys such as ABC-12.
- License 许可
- MIT
- 最近更新
- 2026-11-14
- Stars
- ★ 12
- Forks
- 7
01 前言 Front Matter
- name
- tasks
- description
- Work on or manage records in BB Tasks, including task keys such as ABC-12.
02 资源文件 2
- 参考文档references/attachments.md1.3 KB
- 参考文档references/delegation.md852 B
03 SKILL.md 正文
Tasks
Use the bb tasks CLI to understand the assigned task, keep its record useful,
and report the outcome where the work is tracked.
For task dispatch and execution presets, read references/delegation.md.
Work a task
-
Find and read the task before acting:
bb tasks show ABC-12The detail includes the description, status, priority, labels, subtasks, comments, attachments, attached worker threads, and the GitHub pull requests those threads produced (read from bb's GitHub PR Status plugin, with state open/draft/merged/closed). Use
bb tasks show ABC-12 --jsonwhen the result will drive commands or code. In the JSON, top-levelattachmentsholds the task's own files; each comment lists its files in its ownattachments.For project-wide discovery,
bb tasks listreturns at most 100 rows by default. Pass--limit 1-500; in JSON, continue withnextCursorvia the same filters/sort and--cursor <value>. A task-list mutation makes an old cursor stale, so restart without it. -
Fetch every relevant attachment before making assumptions about it:
bb tasks attachment get <attachment-id> --out <path> -
Do the work. Post one substantive comment at each meaningful milestone, such as a completed investigation, an implementation ready for validation, or a concrete blocker:
bb tasks comment ABC-12 --body "Implemented the change; focused validation now passes."Add
--notifyonly when the new comment should be delivered to the thread that authored the task's most recent agent reply. This resumes an idle recipient; with no prior agent reply, the comment is recorded without targeting an unrelated thread. In agent context, the new comment keeps the current thread identity and an explicit--author, while delivery still targets the prior latest responder rather than the new comment itself. -
Attach result artifacts that belong with the task, such as reports, screenshots, patches, or generated files:
bb tasks attachment add ABC-12 --file ./report.md bb tasks attachment add ABC-12 --file ./screenshot.pngRead
references/attachments.mdfor comment attachments, initial files, removal rules, and machine selection. -
Set the status to match the completion criteria. Use
donewhen they are met, orin_reviewwhen required review remains:bb tasks update ABC-12 --status in_reviewChange task hierarchy with
bb tasks update ABC-12 --parent ABC-10, using either a task key or ID for the parent. Promote a subtask to the top level withbb tasks update ABC-12 --no-parent; the two parent flags cannot be combined.If the work cannot proceed, leave the status accurate and comment with the specific blocker, what you tried, and what would unblock it. Do not mark a blocked task complete.
-
Delegated threads are attached automatically. If this thread was not delegated from Tasks, attach it yourself so the task shows the active work:
bb tasks attach ABC-12When a thread is done with a task (hand-off, respawned replacement, or a predecessor that died), detach it so
bb tasks threads ABC-12stays accurate. Omit--threadto detach the current thread:bb tasks detach ABC-12 --thread thr_dead_predecessor
Link tasks in responses
When your answer refers the user to a task — including a task you just created — emit this leaf directive on its own line instead of writing the key as plain text:
::task{key="ABC-12"}
key is required. Optionally add title="…" as a display fallback shown
while the card loads and when the key no longer resolves. The rendered card
shows the live status, title, and priority, opens the task in the thread
side panel, and links to the full Tasks app. Emit one directive per line;
each renders its own card.
CLI conventions
bb tasks --helplists every command, andbb tasks <command> --helpprints that command's arguments, accepted values, and limits. Both exit 0.--projecttakes a tracker project prefix or id such asABC, never a bb project id (proj_...).bb tasks project listshows both columns.bb tasks statusreports the plugin's name and version. A task's workflow status isbb tasks list --status <status>andbb tasks update ABC-12 --status <status>.- Repeatable options (
--label,--status,--priority,--add-label,--remove-label) accept a repeated flag or one comma-separated list. - Unknown options and stray arguments are errors, never ignored, and every
missing required value is reported in one error. A failing command run with
--jsonprints{"ok":false,"error":{"code","message","hint"?}}on stdout.
Invariants
- Valid task statuses are
backlog,todo,in_progress,in_review,done, andcanceled. - Use
in_reviewwhen implementation is complete but still needs human or agent review. Usedoneonly when the task's completion criteria are met. - Write one comment per meaningful milestone. Combine related facts into a useful update; never spam progress pings, command-by-command narration, or repeated status messages.
- Comments should say what changed or was learned, what validation ran, and any remaining risk or blocker.
- Prefer stable task keys such as
ABC-12for task commands. Use--jsonfor machine-readable output and human output for quick inspection.
04 同仓库更多 Skills
shadcn
Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI, including chat interfaces. Provides project context, component docs, and usage examples. Applies when working with shadcn/ui, component registries, presets, --preset codes, or any project with a components.json file. Also triggers for "shadcn init", "create an app with --preset", "switch to --preset", and for building a design system or applying a DESIGN.md or brand spec to shadcn/ui.
request-review
Request an independent review from the opposite provider (Claude or Codex) of current local agent-session work, including local committed changes or a session proposal, then fix accepted findings and verify.
babysit-pr
Monitor a pull request through review and CI. Use when the user asks to monitor, watch, or babysit a PR.
slopcop
Configure automated GitHub issue and PR rules with the `bb slopcop` CLI. Use for new-issue listeners, pull-request reviews, rule changes, author restrictions, match checks, and shadow results.
secrets
Request user-supplied credentials securely into a dotenv file, or run a command with sudo after the user approves it, without exposing values to the agent.
docs
Read, edit, or save documents in BB Docs vaults, including documents supplied through Docs mentions.