Advanced Dispatcher
by @omaression
Route mid-session work to the right spawned model without changing the fixed main session. Use for coding, architecture, math, algorithms, web development, b...
clawhub install advanced-dispatcher-skillπ About This Skill
name: advanced-dispatcher description: Route mid-session work to the right spawned model without changing the fixed main session. Use for coding, architecture, math, algorithms, web development, brainstorming, research, long-context reading, quick scripts, formatting, multi-model tradeoff evaluation, or structured build pipelines triggered by buildq:, build:, or buildx:. Default to strict no-Claude routing; allow Claude only when the current prompt explicitly includes --force-claude.
Advanced Dispatcher
Classify work, dispatch it to the best spawned model, return the result to the main session.
Non-negotiable rules
--force-claude.--use-claude, --force-opus, --no-opus.--force-claude is prompt-scoped, not session-scoped.openai-codex/* β long cache retention.opencode-go/* β short cache retention.--force-claude is limited to tradeoff proposals.Routing table
| Domain | Model |
|---|---|
| Code & architecture | openai-codex/gpt-5.4 |
| Math & algorithms | opencode-go/glm-5 |
| Web dev & brainstorming | opencode-go/minimax-m2.5 |
| Research & long context | opencode-go/kimi-k2.5 |
| Quick scripts & formatting | openai-codex/gpt-5.3-codex-spark |
Spanning categories β route by highest-risk deliverable: architecture > math > long-context > formatting.
Tradeoff protocol
Trigger when the user compares approaches, evaluates tradeoffs, or asks "which is better."
Default proposals: opencode-go/glm-5 + openai-codex/gpt-5.3-codex
With --force-claude: anthropic/claude-sonnet-4-6 + anthropic/claude-opus-4-6
Judge (always): openai-codex/gpt-5.4
Build pipelines
Trigger on buildq:, build:, or buildx: prefix.
Pre-step: create or verify one short-lived branch for the scoped work.
buildq: (quick, 5 steps)
1. plan βgpt-5.4
2. implement β gpt-5.4
3. test β glm-5
4. simplify β gpt-5.3-codex
5. retest β glm-5build: (standard, 10 steps)
1. parallel-plan-a βgpt-5.4
2. parallel-plan-b β glm-5
3. judge-plan β gpt-5.4
4. boilerplate β gpt-5.3-codex-spark
5. implement β gpt-5.4
6. test β glm-5
7. simplify β gpt-5.3-codex
8. retest β glm-5
9. review-resolve β gpt-5.4
10. final-test β glm-5buildx: (strict, 12 steps)
1. parallel-plan-a βgpt-5.4
2. parallel-plan-b β glm-5
3. judge-plan β gpt-5.4
4. boilerplate β gpt-5.3-codex-spark
5. implement β gpt-5.4
6. test β glm-5
7. simplify β gpt-5.3-codex
8. retest β glm-5
9. review-resolve-a β gpt-5.4
10. test-a β glm-5
11. review-resolve-b β kimi-k2.5
12. final-test β glm-5Exit rule: do not mark the branch PR-ready until automated tests pass and the diff stays atomic.
Judge output contract
Judge-plan must emit: 1. Selected architecture 2. Why it won 3. Project/file structure 4. Implementation order 5. Branch plan (name, scope boundary) 6. Test plan 7. PR/CI test gates 8. Simplification targets 9. Done criteria
For buildx:, also include:
1. Risk list
2. Likely failure modes
3. Review checklist
Simplify contract
Must:
Must not:
Implementation contract
dispatcher.py must produce deterministic RoutePlan objects, expose route choice + cache retention + rationale + pipeline steps, support tradeoff/buildq/build/buildx, reject empty prompts and legacy flags.
Validation checklist
1. Run test_dispatcher.py β all pass.
2. Smoke test tradeoff, buildq:, build:, buildx:.
3. Confirm Claude unreachable without --force-claude.
4. Confirm Claude never in build pipelines.
5. Confirm cache retention correctness.
6. Confirm judge output includes branch plan and PR/CI test gates.