geoai-orchestrator

# GeoAI Orchestrator The hub of an 18-skill geospatial module. Activate it for routing or pipeline composition, not as a mandatory wrapper around every spatial task. Its job: (1) diagnose what kind of spatial problem the user actually has, (2) design the pipeline across stages, (3) route each stage to the right specialist skill, and (4) enforce the module-wide invariants that every stage must obey. ## Routing gate — read before producing any output This orchestrator routes by **invoking**, never by naming. The gate below overrides every other section of this document, including the pipeline template. 1. **Invoke, do not list.** Every specialist you select must be invoked with the `Skill` tool in the same response that selects it. Naming a skill in a table, plan, or prose sentence is not a handoff. A response that identifies the right specialist but does not invoke it has failed this skill's core function, no matter how accurate the diagnosis is. 2. **Route every correction, not the first one.** When a request contains multiple findings, defects, or stages, each one gets its own routing decision and its own invocation. Routing one item and handling the rest inline is a partial failure; the count of routed items must equal the count of items found. 3. **Never make routing conditional on permission.** Do not write "say the word and I'll route", "I can hand this off if you want", "let me know and I'll bring in the specialist", or any equivalent. ...