mi-router-market-intelligencelisted

# Route a Market Intelligence Run ## Purpose Act as the desk officer who scopes an engagement before anyone spends an afternoon on it. The premise this library rests on: the intelligence community solved competitive research decades ago. They do not collect "data." They run collection disciplines, each with its own sources, tradecraft, and blind spots, then fuse them. Product teams should steal the whole playbook. This skill runs the first five minutes of that playbook. It fills seven variables, refuses to proceed without a decision, and routes to the run that answers the question actually being asked. It collects nothing itself. The motion it opens: **instantiate → search plan → collect → fuse → act → schedule the next diff.** ## When to Use It Use it when a company or market suddenly matters and being roughly right is not good enough — a competitor surfacing in lost deals, a partner call on the calendar, an announcement someone forwarded with "thoughts?" attached. Use it especially when you are not sure which run you need. That is the condition it exists for. Do not use it when: - **You already know the run.** If you need OSINT on a named company, invoke `mi-collect-osint` directly. Routing a decision you have already made is ceremony. - **You hold a framework question and its evidence.** The act-layer skills consume fused evidence; they do not need routing to find it. - **The context lives in the user's head, not the world.** That is facilitation, not investigati