Awesome-omni-skill beads-worker

Implement exactly one Beads task in a dedicated git worktree/branch with plan→code→self-review and write full updates back to the task. Use when implementing a Beads task, coding in a worktree, or executing a single task implementation.

install

source · Clone the upstream repo

git clone https://github.com/diegosouzapw/awesome-omni-skill

Claude Code · Install into ~/.claude/skills/

T=$(mktemp -d) && git clone --depth=1 https://github.com/diegosouzapw/awesome-omni-skill "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/tools/beads-worker" ~/.claude/skills/diegosouzapw-awesome-omni-skill-beads-worker && rm -rf "$T"

manifest: skills/tools/beads-worker/SKILL.md

source content

Beads Worker

Orchestrator role

This skill is typically invoked by

$beads-orchestrator

. Users normally start with the orchestrator, not this role.

Input you must obtain from context

Task id (e.g.,
```
bd-a3f8.1
```
)
Worktree path (e.g.,
```
.worktrees/bd-a3f8-1
```
)
Branch name (e.g.,
```
beads/bd-a3f8-1
```
)

Rules

Do not work on multiple tasks.
Do not commit to any other branch.
Before writing code: publish a plan to the Beads task.
Confirm the task already has an Architect Plan update and
```
state=plan-ready
```
before beginning work.
After writing code: self-review, run checks, then publish an implementation summary to the task.
Tests must use the project's existing technologies/infrastructure; do not add new test frameworks without a clear task requirement.
If UI changes are involved: invoke
```
$frontend-design
```
before implementing UI, and follow its guidance.

Tmux integration

Prefer running this skill inside its tmux pane created by
```
scripts/tmux-orchestrator.sh add-worker "$TASK_ID" ...
```
.

If you need to launch a worker from scratch, start the pane with

scripts/tmux-orchestrator.sh add-worker "$TASK_ID" "cd $WORKTREE_PATH && <work commands>"

Procedure

Enter the worktree and confirm branch:
- ```
pwd
```
  ,
```
git status
```
  ,
```
git branch --show-current
```
Read the task:
- ```
bd show "$TASK_ID"
```
Write “Plan” update to task (use template in
```
references/worker-checklist.md
```
).
Implement in small commits:
- commit messages must include the task id.
Self-review:
- review diff vs base branch
- run tests/build
Write “Implemented” update to task:
- summary, verification steps, tests run, commit SHAs
Stop. Do not merge. Hand off to reviewer/integrator.

If you discover out-of-scope work

Do not silently expand scope.
Write a note to the task describing the out-of-scope issue clearly.
Recommend creating follow-up Beads tasks.

If implementation goes wrong (rollback)

If your implementation breaks the build, tests, or introduces regressions:

Stop and assess — do not push more commits hoping to fix forward blindly.
Soft reset option — if recent commits are the problem:
- ```
git log --oneline
```
  to identify the last good commit
- ```
git reset --soft "$GOOD_COMMIT"
```
  to unstage bad changes (keeps files)
- Fix issues, then recommit
Hard reset option — if you need to discard all changes:
- Confirm you are in the assigned worktree + branch:
```
pwd
```
  ,
```
git rev-parse --show-toplevel
```
  ,
```
git branch --show-current
```
- ```
git reset --hard "$GOOD_COMMIT"
```
  (destructive — loses uncommitted work)
Document in Beads — write a note explaining what went wrong and what was rolled back.
Autonomous recovery — if the task is blocked, note it in Beads, attempt a safe workaround or create follow-up tasks, and continue. Halt only if truly catastrophic.