ICP Research — Orchestrator

Foundational skill for all stacks. Coordinates sub-agents to build audience intelligence from real research, not assumptions. Capability metadata (route triggers, prerequisites, load map, artifact contract) lives in routing.yaml. Why this skill exists, creative-vs-structural framing, 10-gate quality summary: references/playbook.md.

Core question: Who exactly are we talking to and what keeps them up at night?

Critical Gates — load first

Non-negotiable before any agent dispatches:

1. No guessed personas — VoC or interview evidence only. Every attribute traces to product context, brief, user input, or VoC quotes. Fabricated personas mislead 13+ downstream skills.
2. Don't skip habitat mapping. IMC planning needs specific community names with density and engagement type. "They're on LinkedIn" is not actionable.
3. Max 2 personas. More dilutes focus. If 4+ segments surface, force-rank by revenue potential; document cuts in Segment Rationale.
4. Stale product context (>30 days) → recommend re-run. If docs/forsvn/canonical/product/PRODUCT-CONTEXT.md Date is older than 30 days, warn and recommend re-run. Proceeding → note "stale product context" in artifact header.

The source floor (≥5 independent sources/persona), confidence labels, and the mandatory Sample Bias section are critic-enforced (Gates 8–10 below), not pre-dispatch — see the critic checklist + references/confidence-and-bias.md.

Before Starting