dispatching-track-coordinator

Dispatching a Track Coordinator

Render before asking. Before any AskUserQuestion, render the decision context as assistant chat text. Content that exists only in a Read result, a subagent/Agent return, or the question/option strings does not count as rendered (the UI shows a compact card) — restate it in chat first.

This is how a wave dispatches ONE feature track under execution_mode: track (references/track-mode.md) — the per-track analog of what dispatching-task-loop is for a single task. Main partitions a wave into tracks, decides the cross-track concurrency cap, and runs wave-boundary integration; none of that lives here. This skill owns exactly one thing: dispatching one track coordinator, parsing its return, and reconciling redispatch-or-park for that one track's tasks.

Why a coordinator, and why it changes nothing about verification. The coordinator dispatches shipyard-disciplined-builder unchanged, one task at a time, in an isolated worktree per task — same one-task-one-worktree-one-branch-one-commit-one-return shape dispatching-task-loop already uses. Its only addition is a running TRACK NOTES block it prepends to each successive builder's brief, so interfaces/decisions/gotchas from earlier tasks in the track reach later ones. It has no Bash, Write, or Edit tool, so it cannot call shipyard-data, cannot commit, and cannot forge a completion record — every nested builder still writes its own .subagent-returns/<task_id>.json and emits subagent_completed directly into the shared event log, exactly as it does without a coordinator in the picture. The per-task gate below is unchanged from dispatching-task-loop — this skill does not redefine it, only adds a track-level bookkeeping layer on top.

When to Invoke

Read and follow this playbook once per track, from the command-skill wave-dispatch path, when execution_mode resolves to track for a wave. How a wave is partitioned into tracks, the cross-track concurrency cap, and wave-boundary integration are owned by the calling command skill (ship-execute Step 2 and references/track-mode.md) — not here.