agentleFS
samuelcastrosamuelcastro/startup-skills/idea-validation/SKILL.md

idea-validation

Skill1 starsChanged 5 months agoMITView on GitHub

Guide founders through validating startup ideas before building. Use when a founder says "I have an idea", "help me validate", "is this a good idea", "should I build this", "customer discovery", or asks about product-market fit, market sizing, or customer interviews. Covers problem discovery, customer interviews, market validation, and go/no-go decisions.

6 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

10 rules. 0 are common, 10 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 6 edited versions we read keep these.

  • 10

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Ask: "Where are you in the journey?"

    line 14
  2. Distinctive:

    Search Reddit, Twitter, Facebook groups, forums for:

    line 48
  3. Distinctive:

    Look for patterns: "too complicated", "missing X feature" = your opening.

    line 68
  4. Distinctive:

    Keep going until clear patterns emerge

    line 75
  5. Distinctive:

    Look for these "lightbulb moments" from successful founders:

    line 83
  6. Distinctive:

    The Mom Test: Don't ask "Would you use this?" — ask "How have you tried to solve this before?" Past behavior > future predictions.

    line 93
  7. Distinctive:

    Nikita Bier principle: Do things that don't scale.

    line 106
  8. Distinctive:

    Create page: "Finally, [solution] for [specific audience]"

    line 109
  9. Distinctive:

    No unfair advantage identified

    line 134
  10. Distinctive:

    Remember: If you have to ask "Do I have product-market fit?" — you don't.

    line 137

“Common” is measured: kept by at least 6 in 10 of the 6 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Idea Validation

Guide founders from raw idea to validated hypothesis with confidence to commit or kill.

Workflow

1. Diagnose Stage

Ask: "Where are you in the journey?"

StageSignalsNext Step
Raw idea"I'm thinking about..."→ Go to Step 2
HypothesisHas problem + solution defined→ Go to Step 3
InterviewedTalked to 5+ people→ Go to Step 4
TestingHas MVP/landing page→ Go to Step 5

2. Shape the Hypothesis

Help founder articulate three components (Kevin Hale/YC framework):

  1. Problem: What burning pain exists? Who has it?
  2. Solution: What's the experiment/MVP?
  3. Insight: Why will YOU win? (unfair advantage)

Unfair advantages to probe for:

  • Founder-market fit (lived the problem, domain expertise)
  • Market timing (20%+ annual growth)
  • 10x better product possibility
  • Built-in distribution/word-of-mouth
  • Network effects potential

Output: One-sentence hypothesis in format:

"[Target customer] struggles with [problem] because [root cause]. We believe [solution] will work because [insight/unfair advantage]."

3. Validate the Problem

Quick Validation (60 min) — Tom Bilyeu Method

For rapid signal-checking before deep interviews:

Problem Hunt (15 min) Search Reddit, Twitter, Facebook groups, forums for:

  • "Why is there no..."
  • "I wish someone would make..."
  • "I've tried 5 different solutions..."
  • "Paying $X but it doesn't even..."

Collect 10 specific complaints. Can't find 10? Different problem.

Size Check (10 min) Google Trends + Keyword Planner:

  • <1K monthly searches = Dead
  • 1K-10K = Niche (can work)
  • 10K-100K = Solid opportunity
  • 100K+ = Major market

Competition Map (15 min) Find top 5 competitors. Check pricing pages + 1-star reviews.

  • Pricing <$50/mo + bad reviews = struggling market
  • Pricing $100+ with good reviews = profitable space

Look for patterns: "too complicated", "missing X feature" = your opening.

Deep Validation — Customer Interviews

How many conversations?

  • B2C with uniform behavior: ~20 interviews
  • B2B with varied buying patterns: 50+ interviews
  • Keep going until clear patterns emerge

See references/interview-guide.md for question scripts and signal detection.

Critical rule: Anything short of "I want this!" is really "No thanks."

4. Assess Market Pull

Look for these "lightbulb moments" from successful founders:

SignalStrengthExample
Polite interest❌ Weak"Sure, I'd check it out"
Unsolicited referrals✅ StrongPeople you didn't talk to reach out
Interrupted pitch✅ Strong"Wait, you can do WHAT?"
Pre-purchase on mockup✅ StrongSigned customers from Figma prototype
Inbound after launch✅ Strong133 leads in 72 hours (Pinwheel)

The Mom Test: Don't ask "Would you use this?" — ask "How have you tried to solve this before?" Past behavior > future predictions.

5. Test Before Building

Choose validation method based on idea type:

Idea TypeValidation Method
B2B SaaSSell on mockups/Figma before code
Consumer appSimulate populated experience in Figma
MarketplaceValidate BOTH sides separately
Dev toolsLeverage personal network first, then SEO content

Nikita Bier principle: Do things that don't scale. Make it the BEST it could ever be manually. If it works, then automate. If you only launch the "scalable" version, you won't know if it failed due to concept or execution.

Landing page test (if applicable):

  • Create page: "Finally, [solution] for [specific audience]"
  • Run $20-50 in ads
  • Conversion benchmarks:
    • <1% = Kill immediately
    • 2-5% = Test further
    • 5%+ = Build immediately

6. Decision Checkpoint

GO Signals

  • People reaching out unprompted
  • Strong reactions in interviews ("I need this")
  • Pre-sales or LOIs on mockups
  • Clear pattern in 20+ conversations
  • You have an unfair advantage

PIVOT Signals

  • Adjacent problem keeps coming up
  • Different customer segment more excited
  • Core insight valid, solution wrong

KILL Signals

  • Lukewarm reactions after 20+ interviews
  • Have to "convince" people of the problem
  • Can't find 10 complaints in 15 min searching
  • No unfair advantage identified
  • Market too small (<1K searches, <$1B TAM)

Remember: If you have to ask "Do I have product-market fit?" — you don't. When you have it, you know.

Common Traps

See references/traps.md for the 7 deadly traps and how to avoid them.

Reference Files

  • references/frameworks.md — All 5 validation frameworks in detail
  • references/case-studies.md — 8 founder stories (Vanta, Flexport, etc.)
  • references/interview-guide.md — Question scripts + what to listen for
  • references/traps.md — 7 traps with detection and avoidance

Adapted from Linas Beliūnas's The One-Person Unicorn founder skill set.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.