pilot-wavelisted

# pilot-wave — compose and launch a delegated card/wave This skill turns "drive these cards for me" into a correctly-briefed delegation. It resolves the **environment brief** for the current machine and project, selects the cards, and composes the spawn prompt for the project's adopted `pilot-orchestrator` (a wave) or a single `pilot` (one card). The agents do the dev loop; your main session stays a thin relay that owns wake-ups and hard escalations. **Adoption is a PREREQUISITE, not an option.** The pilot suite ships as unregistered templates (`plugin/agent-templates/`) precisely because Claude Code silently ignores the `observer:` field on a plugin-REGISTERED agent — there is no namespaced "workflow-toolbox: pilot" type to fall back to. A pilot only exists to spawn once its definition has been adopted into the project's `.claude/agents/` under its bare name (see Step 3). If the project has no adopted copy yet, propose the adoption before spawning anything. Use it when the user wants tracked cards driven autonomously. For a one-off mechanical edit, skip this — a plain sub-agent (or doing it yourself) is simpler. ## The delegation ladder (the principle this skill applies) Route work to the lowest rung that fits, and **pin model + effort at every spawn — never let a delegate silently inherit the session's model**: | Work | Rung | Who | |---|---|---| | A question / analysis / arbitration | your main loop, inline | you | | One isolated mechanical chore | one throwaway sub-