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.