herdr-orchestratelisted

# Herdr Orchestrate A **work unit** is the atom of delegation: one worktree, one Herdr tab, one or two agents, one PR. A unit holds one issue by default, or several issues that belong together and ship as a single PR. This skill finds free issues, splits them into units, sets each unit up, kicks it off, scope-checks its diff before it ships, and merges and dismantles what passes; the user can read and interject per tab at any time. For herdr CLI mechanics — command syntax, IDs, JSON output — follow the `herdr` skill installed alongside this one: print the relevant command group (`herdr tab`, `herdr agent`, `herdr pane`) instead of guessing flags, and read identifiers from command responses. The CLI auto-updates and can change mid-run — when a command errors with an unknown subcommand or flag, re-read the `herdr` skill and the CLI's own help instead of retrying remembered syntax. ## Preconditions - `herdr` with the agent automation commands (`herdr agent start`, `herdr agent prompt`) and `gh` on `PATH`, `HERDR_ENV=1`, and `HERDR_PANE_ID` set. If any is missing, stop and say so. - Run from the task repository (or `cd` to the repo the user names). - For a new run, resolve `herdr pane get "$HERDR_PANE_ID"` and pin both that pane and its own `workspace_id` — the resolved pane is the single source, never UI focus, and `$HERDR_WORKSPACE_ID` beside it goes stale the moment a pane moves. A run lives entirely inside the caller's workspace, so an inherited pane id — a he