Orchestrate herdr

Fan a spec's open sub-issues out to one herdr-managed worker tab each and drive each to a test-backed end state. You are the orchestrator: never implement, never close your own tab.

Inputs

SPEC_REF is resolved first, from skill args (SPEC_REF=..., or a bare spec reference; legacy SPEC_URL=/PRD_URL= keys accepted) and otherwise by asking. The rest are settled at Intake. Never guess an input.

• SPEC_REF — the spec (PRD) or parent issue whose open sub-issues become workers, in its tracker's native form: a Linear issue ID (PRWL-100, ABC-123) or a GitHub issue URL or number.
• AGENT — which coding agent runs the workers, named from the six supported runtimes. It yields two values that are not interchangeable: CLI_NAME, its launch token, used for PATH checks and tab labels; and AGENT_KIND, its herdr --kind. Both come from the roster in references/intake.md — never from a command's first token, which is wrong for Cursor.
• CODING_CLI — CLI_NAME plus the permission-mode flags the user picks. The prompt is never a launch argument (see Rules).
• ISOLATION — worktree, branch, or shared; it decides whether workers can run in parallel.
• TRACKER / TRACKER_TAG — the workspace's tracker of record and its tag — GitHub G, Linear L. Derived, not asked: resolve per Resolve in references/tracker-map.md, which holds the per-tracker commands cited by bold section name below.

Rules

• Zero attribution. Omit co-author, AI, and tool attribution from prompts, commits, tracker comments, and reports.