account-sourcinglisted

# Account Sourcing Turn an ICP from a strategy document into pipeline: a ranked list of real accounts worth pursuing, each with public evidence for why, and a visible reject pile. This skill is opinionated about one thing: **an account belongs on the list only if you can point to the evidence, and a list that shows no rejects is hiding its judgment.** The first deliverable companies expect from go-to-market engineering is exactly this: the target account list, mapped to ICP criteria, scored, and refreshed. Outreach comes later and depends on it. ## What this builds (and what it doesn't) - **It builds** the account layer: a ranked, evidenced account list (`account-list.md`), a machine-readable handoff (`accounts.json`) shaped for Clay, a CRM, or a sequencer, and the scoring rubric used (`rubric.yaml`). - **It does not draft outreach.** Signal-to-message work belongs to `outbound-engine`, which consumes this skill's output. It also does not harvest individuals: sourcing stays at the account level, with a suggested entry role per account taken from the ICP's buying committee. People come later, at outreach time, at role level. ## Fit and limits Built for products **bought by organizations** (a team or committee buys). For individual-buyer products, "accounts" is the wrong unit: sourcing there means finding channels and communities, which the ICP's journey section already maps. Say so and stop rather than forcing an account frame. ## Inputs (ask for what is missi