worker-workflow

Task Execution Workflow

This skill provides the complete 8-phase lifecycle for executing teamwork tasks using native Claude Code APIs. Follow these phases in order.

---

Structured Description Convention

The orchestrator creates tasks with structured markdown sections in the description. Workers MUST parse these sections to determine approach, criteria, and verification commands.

## Description
What needs to be done

## Approach
standard | tdd

## Success Criteria
- Criterion 1
- Criterion 2

## Verification Commands
npm test -- path/to/test
npx tsc --noEmit src/file.ts

Parsing rules:

Section	Required	Default
## Description	Yes	N/A
## Approach	No	standard
## Success Criteria	No	Use general evidence collection
## Verification Commands	No	Skip automated verification

Workers extract these sections from the task description after claiming. If ## Approach is missing, default to standard. If ## Success Criteria is missing, use general evidence collection.

---

Phase 1: Find Task

List available tasks using native TaskList:

# List all tasks in the team
tasks = TaskList()

Filter for tasks that are:

• Unblocked: No pending dependencies (all blockedBy tasks are completed)
• Unowned: No owner assigned yet
• Open: Status is not completed or in_progress

If your agent has a role specialization, prioritize tasks matching your role.

If no task found: Send a message to the orchestrator and wait for assignment.

SendMessage(
    type="message",
    recipient="orchestrator",
    content="No available tasks matching my role. Waiting for assignment.",
    summary="Worker idle - no tasks available"
)

---

Phase 2: Claim Task

Claim the task by setting yourself as the owner and updating the status:

TaskUpdate(
    taskId="<TASK_ID>",
    owner="<your-agent-name>",
    status="in_progress",
    activeForm="Working on: <task subject>"
)