Herdr Orchestration

Treat the current agent session as the control tower, regardless of its CLI or model. Keep decomposition, routing, integration, user communication, and final review in this host session.

Load and follow the herdr skill before issuing Herdr commands. Continue only when HERDR_ENV=1, and use the installed CLIs as the authority for supported launch options. Herdr's discovery commands print their help and exit 2; treat that as success for discovery and do not run them under set -e.

Topology

The herdr skill governs command mechanics and safety. Where its defaults disagree with this skill — sibling-pane topology, no new tabs, or its --wait-at-prompt guidance — this skill wins: an orchestration run is an explicit request for this topology and this dispatch behavior.

Keep the control tower and every worker in the current Herdr workspace. Leave the control-tower pane in its existing tab. Create worker tabs in that workspace, group related workstreams in the same tab, and cap each worker tab at four panes:

herdr tab create --workspace "$HERDR_WORKSPACE_ID" --cwd "$PWD" --label "<role>" --no-focus
herdr pane split --pane <worker-pane-id> --direction right --cwd "$PWD" --no-focus

Read result.tab and result.root_pane from the create response. herdr tab create already returns a root_pane, so count it against the cap rather than splitting a spare. Split from a worker pane, never --current, which is the control tower. Split a wide pane to the right and a tall one down. Reuse a matching tab this run created while it has capacity; otherwise create another clearly named tab. Never place a worker in a tab belonging to another session.