nebi-orchestrationlisted
Install: claude install-skill romanized/nebi-skill
# Orchestration: route work without collisions
The active harness's core override always wins, including any model, mode, or method Nebi named. Carry an explicit model choice through the dispatch tool when the harness exposes that control.
## Choose from dependencies and collision risk
Map dependency direction, edit overlap, shared resources, and uncertainty before considering task size or agent availability. When the fan-out, loop, or ordering is knowable in advance, script it rather than letting a model re-decide each step. Use the least coordination that preserves clear ownership and proof:
- **Solo:** one lead owns work whose files, decisions, or dependencies are tightly coupled.
- **Scout:** one or more read-only workers gather heavy or independent evidence; the lead resolves contradictions and synthesizes. Unknown-size discovery repeats rounds until a round returns nothing new or a stated cap is reached.
- **Serial workers:** hand off in dependency order when one output defines the next, or writers would share a file, resource, or decision.
- **Parallel isolated writers:** use only with disjoint write scopes, satisfied dependencies, stable interfaces, and independent acceptance checks.
- **Competing hypotheses:** assign read-only, falsifiable investigations; the lead or named arbiter chooses, then one owner implements.
- **Generate and judge:** when the job is choosing among open-ended options (names, designs, rankings), generate candidates, then judge them against