targeted-searchlisted

# Targeted Search A thin stage wrapper around the list-builder engine in `engine/list-builder/`. The engine owns the process; this skill owns getting the run's ICP into it and its result back out. **Read `engine/list-builder/RUNBOOK.md` before running anything.** Run the commands there; do not improvise. `engine/list-builder/SKILL.md` documents every phase and env var. ## Pipeline contract **Stage 7 of 20.** Reads `01-seeds.csv`, `02-client-profile.yaml`, `03-lookalikes.csv`, and the company domains in `06-audience-qualified.csv`. Writes `07-judge-spec.json`, `07-lane.json`, `07-accounts.csv`. Files live in `runs/<run>/`. Column definitions: [`/prospecting-system`](../prospecting-system/SKILL.md). ## Steps 1. **Build `07-lane.json`** from the profile (shape documented at the top of `engine/list-builder/scripts/run-lane.ts`): - `seeds` ← `01-seeds.csv` - `emp_min` / `emp_max`, `states`, `industries` ← `icp_hard_filters`. Industry names must be valid Prospeo names (`skills/icp-definition/references/prospeo-industries.md`). - `keywords` ← the discriminating phrases from `01-customer-patterns.md` - `seniorities` ← the profile's titles - `extra_candidates` ← absolute paths to `03-lookalikes.csv` and a `domain`-column CSV of the companies behind `06-audience-qualified.csv`. This is how both lanes land in one judged list. 2. **Judge prompt** — reuse the ICP and disqualifiers the human approved in stage 6. Write `07-judge-spec.json` and generate the prompt with