00-gtm-router

# GTM Router - the orchestrator (00) Every other skill in this chain wraps a tool. This one wraps the decision: given an ICP, which chain do you run, in what order, at what depth, and what will it cost. Tool-routing ("use Firecrawl for scraping") is table stakes; this skill does methodology-routing - the shape of the ICP picks the discovery path, volume picks the extraction depth, evidence type picks the signal source, every discovered list passes the qualification gate (01-icp-qualify) before credits are spent on it, and everything funnels through judgment (05) before anyone writes an email. Two model-judgment layers bracket the paid steps: the gate decides who is worth paying to know more about, the judge decides what to say to them. The router itself spends nothing. All credits are spent inside component skills, each of which keeps its own spend gates. The router's job is to make the spend deliberate: plan first, estimate honestly, execute only after a go-ahead, and checkpoint between steps. ## Inputs - **icp_description** (required) - who the client is targeting, in plain English. - **icp_context** - what the client sells, to whom, and what pain it removes (2-4 sentences). 05-signal-builder cannot judge without it, so collect it during planning, not four steps in. If it's missing, ask once. - **exclusions** (optional, ask once) - competitors, current customers, do-not-contact domains. The gate (01-icp-qualify) enforces them for free; discovery skills also appl...