herdr-dispatchlisted

Dispatch peer coding agents through Herdr using assign, handoff, and send_message. Use when inside a Herdr pane and the user wants Claude, Codex, Pi, omp, Grok Build, Cursor, or another CLI worker spawned, tasked, collected, or followed up. Triggers include herd-dispatch, assign a worker, handoff to Codex, send_message to a pane, fan-out agents, peer review across CLIs, grok-build worker, cursor-agent model.
arronKler/herdr-skills · ★ 15 · Code & Development · score 81

Install: claude install-skill arronKler/herdr-skills

# Herdr Dispatch Captain protocol for running other coding CLIs as workers inside Herdr. Call the bundled script. Do not improvise raw `herdr agent start` / `wait` / `prompt` sequences. ## Preconditions 1. Run `scripts/herd-dispatch doctor` first. It must report `"ok": true`, `"herdr": true`, and `self.pane_id`. 2. If doctor prints `"ok": false` for any reason (including `HERDR_ENV!=1`, missing verbs, or unresolved captain pane), stop. Show the JSON to the human. Do not debug by running raw `herdr agent` commands. 3. Never target the captain pane. The script refuses self-operations; do not bypass it. 4. Never run bare `herdr` (that attaches the TUI and hangs). Do not run bare `herdr agent` either; kinds come from doctor JSON or `herdr agent start --help`. 5. Workers must not dispatch further workers. Only the captain uses this skill. ## Tools All verbs print JSON. Read `ok`, `name`, `status`, `delivery`, `deliverable`, `result_excerpt`, `error`. `status` is the Herdr lifecycle: `idle`, `done`, `working`, `blocked`, or `unknown`. It is never `settled`. For dispatch/collect, `ok` describes lifecycle, not work quality: - `assign` / async `send`: delivery is confirmed and status is `working` (or `idle`/`done` if it already finished). - `handoff` / `collect` / `send --wait`: delivery is confirmed and status is `idle` or `done`. - `delivery: unconfirmed`: the prompt may already have arrived. Use `watch` or inspect; do not resend or replace the worker merely because of this