dispatching-worklisted

## Prepare the dispatch The caller resolves the app and execution tier. This skill owns instruction creation, launch, checkpoint handling, and cleanup. [boss-say](../boss-say/SKILL.md#plan-and-schedule) owns plan scheduling; a `batch` label only groups dispatches. Before writing an instruction, confirm `herdr status` and the current `$HERDR_PANE_ID` live record. Report an unavailable dependency and continue dispatch only from a reachable Herdr session. Resolve the worker's provider/profile/model/effort through [work-route resolution](references/dispatch-mechanics.md#resolve-mode-and-work-route), map the main agent's restriction tier through [permission mapping](references/dispatch-mechanics.md#permission-mapping), and state the selected setup and reason. Register through [contacting-orchestrators](../contacting-orchestrators/SKILL.md), then record this session's pane and provider fingerprint using [Record the main agent before launch](references/cross-session-coordination.md#record-the-main-agent-before-launch). Team-mode cwd preparation belongs to [shipping-task](../shipping-task/SKILL.md#prepare-and-execute). ## Write the brief Carry the user requirement, requested outcome, dependencies, and verified coordination facts already available. Target-app context discovery and work decisions stay with the worker in its own harness, so the brief carries only what the worker cannot reach from there. Investigation and audit briefs request an explanatory result with evidence refe