validate-icp
Validate ICP
Prove an ICP hypothesis exists publicly — in their own words — before asking the user to invest in interviews.
Goal
VALIDATED verdict backed by 25+ verbatim quotes, 10+ named individuals to DM, and a reachability scorecard.
WEAK or NOT FOUND verdicts are equally valid outputs. A NOT FOUND result backed by evidence saves the user weeks of interview work and routes them to pivot ICP or run cold outreach instead.
Workflow
Phase 1 — Lock the ICP hypothesis
Confirm three elements before searching. If any are vague, tighten with the user first.
- Who — role/profile, not demographics (e.g. "indie SaaS founder who shipped on Lovable" not "startup founder")
- Circumstance — when the job arises (e.g. "already shipped, between weeks 1–90")
- Hypothesized pain — what they're struggling with (gives the search its verbs)
Phase 2 — Map the search surface
Default surfaces — skip any the ICP doesn't live on:
- Reddit — named subs (r/SideProject, r/SaaS, r/indiehackers, r/Entrepreneur, or vertical-specific)
- Hacker News — Algolia search (hn.algolia.com) + known thread IDs
- X / Twitter — named accounts + quote-tree mining of canonical incidents
- IndieHackers — post + comment search
- Trustpilot / G2 / Capterra — if ICP uses specific tools with reviews (filter 1–3 star)
- LinkedIn — public posts + Pulse long-form (Google Site Search only)
- Discord / Slack — only publicly indexed transcripts
- Facebook Groups — only public groups via Google Site Search
- Niche forums — domain-specific (BiggerPockets, PracticalMachinist, etc.)
Phase 3 — Spawn parallel agents (one per surface)
Use the agent brief template in REFERENCE.md. Every brief MUST:
- Front-load 300–400 words of ICP context (agents start cold)
- Name specific search targets (subreddits, usernames, thread IDs, product URLs)
- Specify output format (raw quotes, source-linked, categorized by 6 buckets)
- Include the anti-instruction: "Do not synthesize or paraphrase. Return verbatim quotes."
Fetch strategy — tracer bullet + fail fast. Most high-value surfaces (Reddit, X, G2, Capterra, LinkedIn) block direct agent fetches. Every agent brief MUST include the fetch protocol from REFERENCE.md:
- Before the sweep, run one tracer-bullet fetch against a known-good URL on the surface using the top of that surface's loophole ladder.
- If it works, commit to that method. If it fails, drop one rung and retry the same tracer URL.
- Descend until one rung works, or until the full ladder fails on the tracer — then abort the surface and report
BLOCKED. Never fabricate. Never burn more than ~3 attempts on a blocked URL. - Mid-sweep, after 2 consecutive failures on the committed method, re-run the tracer from the top.
Per-surface loophole ladders (Reddit, X, G2/Capterra, LinkedIn, Discord, Facebook) live in REFERENCE.md.
Run agents in parallel — surfaces are independent.
Phase 4 — Synthesize into verdict
Consolidate outputs into the report template in REFERENCE.md. Score on four axes (0–3 each, full rubric in REFERENCE):
- Pain visibility — how loudly they talk about the pain publicly
- Reachability — which channels yield named individuals at scale
- Purchasing power signals — evidence of budget (MRR mentions, tool spend, titles)
- Population size — rough count of distinct voices found
Render verdict: VALIDATED (≥9, no axis at 0), WEAK (5–8 or any 0), NOT FOUND (≤4).
When to stop and pivot
If the full sweep yields fewer than 10 distinct verbatim quotes, the ICP may only exist privately (common for enterprise buyers, regulated industries, shy verticals). Report NOT FOUND and route to:
- Cold outreach — ICP is targetable but not vocal
- Pivot ICP — hypothesis is wrong; re-tighten and rerun
- Proxy interview — ICP is gated; interview an adjacent role
Ethical boundaries
- Never fabricate quotes. No source URL = no inclusion.
- Always link the source. Include date where visible.
- Don't contact anyone. Produce the DM list — the user decides who to reach.
- Respect platform norms. Public commentary is fair to quote; paid/gated community content is not.
Composition with other skills
- Runs after
jobs-to-be-done(consumes the ICP hypothesis) - Runs before
mom-test(produces interview targets + non-leading language) - Feeds
hundred-million-offers,storybrand-messaging,obviously-awesome(verbatim pain becomes copy)
Advanced
See REFERENCE.md for:
- Full agent brief template (copyable)
- Community-by-community search tactics
- Scoring rubric
- Output report template
- Strong-vs-weak signal classification
See EXAMPLES.md for a worked example.
More from ivcota/skills
faas
|
9the-one-thing
Narrow focus to extraordinary results using Gary Keller's Focusing Question, Goal Setting to the Now, and Time Blocking. Use when the user mentions "the ONE Thing", "focusing question", "time blocking", "domino effect", "go small", "lead domino", "goal setting to the now", "80/20", "Pareto", "Three Commitments", "Four Thieves", "E to P", or "counterbalance". Also trigger when cutting a bloated to-do list, picking a team's top priority or OKR, designing a daily schedule around deep work, deciding what to say no to, diagnosing overwhelm or work-life-balance problems, planning a product roadmap around a single bet, or when effort is not producing results. Covers the ONE Thing principle, the Six Lies of success, the Focusing Question, Goal Setting to the Now, Time Blocking, the Three Commitments, and the Four Thieves. For habit formation mechanics, see drive-motivation. For product positioning around a single bet, see obviously-awesome. For persuading a team to adopt one priority, see made-to-stick.
4office-hours
|
4distill-to-skill
|
4e-myth-revisited
|
4good-strategy-bad-strategy
Write, diagnose, and audit strategy using Richard Rumelt''s Kernel (diagnosis, guiding policy, coherent action), the Four Hallmarks of Bad Strategy, and the Nine Sources of Power. Use when the user mentions "is this a real strategy", "our strategy is just goals", "diagnose our strategy", "strategy is fluff", "kernel of strategy", "guiding policy", "coherent action", "bad strategy", "strategic objectives", "dog''s dinner of goals", "failure to face the challenge", "proximate objective", "chain-link", "competitive advantage", "leverage", "focus", "dynamics", or "inertia". Also trigger when reviewing a strategy deck, auditing a roadmap for substance, cutting fluff from a plan, defining the real problem before planning, or diagnosing why a strategy is not producing results. Covers the Kernel, the four hallmarks of bad strategy, and the nine sources of power. For tech adoption strategy, see crossing-the-chasm. For blue-ocean value innovation, see blue-ocean-strategy. For positioning, see obviously-awesome.
3