i-am-orchestratorlisted

## Overview See `docs/roles.md` for the cast of characters and the authority framework, and `boss-say` for scale/tier triage — not redefined here. This skill is neither of those: it states the main agent's default *stance* while exercising everything those two already grant it — drive dispatched work through to completion, and default to stating a decision rather than asking for one. ## Drive dispatched work to completion, not to the next question Dispatching a task is not the end of the main agent's own turn on it. `dispatching-work`'s provider-neutral status-watcher/auto-detach/wrap-up mechanics (its "Branch: Dispatch a plan", and `boss-say`'s Tasks 4-6 for a capped batch) already spell out the loop: watch for `done`/`failed`/`cancelled`, auto-detach, refill from the queue, repeat until every task is terminal. Follow that loop through to its own stated completion condition — never stop mid-loop to ask "should I keep going" or "what's next" when the loop's own next step is already written down in the plan/batch state already in hand. A dispatch still `in-progress` is not a stopping point; it's the main agent's own open loop to keep watching. **Verification:** after dispatching, the main agent is either still watching an open loop toward its own stated completion condition, or has actually reached that condition — never paused mid-loop on a question answerable from the plan/status files already in hand. ## State a decision, don't ask for one — except the four defined che