Worker

Worker Skill: Autonomous Bead Execution

Executes beads within an assigned track, maintaining context via Agent Mail.

┌─────────────────────────────────────────────────────────────────────────────┐
│  TRACK LOOP (repeat for each bead in track)                                 │
│                                                                             │
│  ┌──────────────┐   ┌──────────────┐   ┌──────────────┐                    │
│  │ START BEAD   │ → │ WORK ON BEAD │ → │ COMPLETE     │ ──┐                │
│  │              │   │              │   │ BEAD         │   │                │
│  │ • Read ctx   │   │ • Implement  │   │ • Report     │   │                │
│  │ • Reserve    │   │ • Use tools  │   │ • Save ctx   │   │                │
│  │ • Claim      │   │ • Check mail │   │ • Release    │   │                │
│  └──────────────┘   └──────────────┘   └──────────────┘   │                │
│         ▲                                                  │                │
│         └──────────────────────────────────────────────────┘                │
└─────────────────────────────────────────────────────────────────────────────┘

Initial Setup (Once Per Track)

1. Register Agent Identity

Tool: mcp__mcp_agent_mail__register_agent

Name auto-generated if omitted (e.g., BlueLake)

2. Understand Your Assignment

From orchestrator: Track number, Beads (in order), File scope, Epic thread (<epic-id>), Track thread (track:<AgentName>:<epic-id>)

Bead Execution Loop

Step 1: Start Bead

1.1 Read Context from Previous Bead

Tool: mcp__mcp_agent_mail__summarize_thread

1.2 Check Inbox

Tool: mcp__mcp_agent_mail__fetch_inbox

1.3 Reserve Files

Tool: mcp__mcp_agent_mail__file_reservation_paths

If conflict → report blocker (see reference/message-templates.md)

1.4 Claim Bead

bd update <bead-id> --status in_progress
bd show <bead-id>

Step 2: Work on Bead

2.1 Explore Codebase

Tool: mcp__gkg__search_codebase_definitions

Tool: mcp__gkg__get_references

2.2 Make Changes

Use built-in file editing tools for code changes.

After edits: get_diagnostics("<edited-file>")

2.3 For UI Work

Load frontend-design skill first, then follow this workflow:

2.3.1 Search for Components

Tool: mcp__shadcn__search_items_in_registries

2.3.2 View Component Details

Tool: mcp__shadcn__view_items_in_registries

2.3.3 Get Usage Examples

Tool: mcp__shadcn__get_item_examples_from_registries

2.3.4 Install Component

Tool: mcp__shadcn__get_add_command_for_items

Then run the returned command (e.g., npx shadcn@latest add button).

2.3.5 Verify Installation

Tool: mcp__shadcn__get_audit_checklist

2.4 Check Inbox Periodically

Use mcp__mcp_agent_mail__fetch_inbox with since_ts parameter.

2.5 If Blocker or Interface Change

See reference/message-templates.md for message formats.

Step 3: Complete Bead

3.1 Verify & Check

get_diagnostics("<project-path>")
bun run check-types
bun run build

3.2 Close Bead

bd close <bead-id> --reason "<concise summary>"

3.3 Report to Orchestrator

Tool: mcp__mcp_agent_mail__send_message

3.4 Save Context for Next Bead

Self-addressed message to track thread. See reference/message-templates.md.

3.5 Release Reservations

Tool: mcp__mcp_agent_mail__release_file_reservations

Step 4: Continue to Next Bead

Loop back to Step 1. Context from Step 3.4 available via track thread.

Track Completion

When all beads done, send track complete message (see reference/message-templates.md), then return:

Track N (<AgentName>) Complete:
- Completed beads: a, b, c
- Summary: <what was built>
- All acceptance criteria met

Quick Reference

Bead Lifecycle Checklist

START: summarize_thread → fetch_inbox → file_reservation_paths → bd update
WORK:  gkg tools → morph edits → get_diagnostics → check inbox
DONE:  verify → bd close → send_message (orchestrator) → send_message (self) → release
NEXT:  loop to START

Thread Reference

Tool Reference

Additional Resources

• Message Templates: reference/message-templates.md for all Agent Mail message formats