model-orchestration
Installation
SKILL.md
Model Orchestration
Route by task capability and risk, not by hardcoded provider, model tier, or effort label.
Workflow
- Read references/routing.md and the repository’s delegation rule.
- State the shared goal, acceptance criteria, authoritative sources, and non-goals.
- Separate deterministic work from judgment. Run deterministic transforms with code or tools.
- Delegate only bounded work with a clear deliverable. Parallelize only tasks that do not depend on each other’s result.
- Assign exclusive file or subsystem ownership for every writer. Use isolated workspaces when write sets may overlap.
- Pass each worker the objective, output format, sources, boundaries, permissions, and evidence required.
- Keep the parent responsible for synthesis and verification. A worker’s report is evidence to inspect, not a completion claim to forward.
- Reconcile conflicts explicitly. Prefer the result supported by stronger, more current evidence and record the rejected alternative.
- Stop completed workers when the runtime requires cleanup. Report unsupported delegation features honestly.