icp-definitionlisted

# ICP Onboarding ## Pipeline contract **Stage 2 of 20.** Reads `01-customer-patterns.md` and `00-customers.csv`. Writes `02-client-profile.yaml`. - Pre-fill the interview from `01-customer-patterns.md` — propose answers, let the human correct them. Never skip the hard-vs-soft split. - Put every domain from `00-customers.csv` into `excluded_domains`. - Save to the run folder (`runs/<run>/02-client-profile.yaml`), not the `~/cold-email-ai-skills/` path below. - Tiering and persona depth: `references/icp-matrix-builder.md`, `references/persona-development.md`. - Done when the human has confirmed the yaml. Files live in `runs/<run>/`. Column definitions: [`/prospecting-system`](../prospecting-system/SKILL.md). Standalone use: ignore this block. Conversational intake. The user arrives with a business; this skill produces a `client-profile.yaml` every other skill in the repo consumes. Without it, downstream skills guess at targeting and write generic copy. ## Why this exists Most cold email fails because the sender didn't define the ICP tightly enough. "B2B SaaS founders" is not an ICP. "VP of RevOps at 50-500 person B2B SaaS companies in the US that raised Series B in the last 12 months" is an ICP — you can put it into Prospeo and get a list. This skill forces that precision up front. It also separates **hard filters** (must match) from **soft preferences** (nice-to-have), because the #1 mistake beginners make is treating every ICP criterion as required, ending up with a