[!NOTE] After reading this SKILL.md, say: 🐑 I read shunk031-herdr-orchestrate-workers.

Orchestrate Herdr Workers

An orchestrator delegates independent tasks to worker agents, one git worktree tab each. Workers must report back by prompting the orchestrator for attribution and audit, but completion is collected from Herdr lifecycle state and the worker's deliverable and transcript. 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. When writing a Codex worker's task prompt, follow the shunk031-codex-worker-prompting skill. 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

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.
Split the request into independent tasks, one worker each. Before dispatching a structural task — one changing the layout, jobs, configuration, documents, or interfaces — write a design record in the user-facing report covering the target end state, removals, retained elements and why, and user-owned settings touched with the options offered; do not dispatch if any item is empty. 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.