Orchestrate Herdr Workers

An orchestrator delegates independent tasks to worker agents, one git worktree tab each; workers report back by prompting the orchestrator, and normal completion remains report-driven without coordinator polling. Read this skill file and the herdr skill first: the herdr skill owns all CLI mechanics, JSON responses, ID handling, and safety rules. This skill adds only the orchestration protocol. Build every peer prompt in a shell variable first (for example, with a quoted heredoc) and pass it as one argument; never let the shell expand task or report text.

Set up the orchestrator

1. Name yourself so workers can address you, and label your tab. Pick a short name that is free in herdr agent list; names cap at 32 characters:

   herdr agent rename "$HERDR_PANE_ID" orch
   herdr tab rename "$HERDR_TAB_ID" "🤖 Orchestrator"
   

   A worker promoting itself to sub-orchestrator skips this step: it keeps the agent name and tab its parent already tracks.

2. Split the request into independent tasks, one worker each. Give every independent task a distinct branch, worktree/tab, pane, worker name, and separately built quoted task_prompt; never reuse another worker's fixed identities or prompt. Keep sequential or trivial work yourself. Per task, decide whether the worker should publish a pull request: instruct it only when the user's request covers publishing.

Launch each worker