validate-idea
Stress-test a startup idea before any code is written. Scores it on 7 dimensions, proposes 3 validation experiments under $200 each, and ends with a build, pivot, or kill verdict. Use when a founder asks whether an idea is worth building.
- License 许可
- MIT
- 最近更新
- 2026-11-03
- Stars
- ★ 839
- Forks
- 72
01 前言 Front Matter
- name
- validate-idea
- description
- Stress-test a startup idea before any code is written. Scores it on 7 dimensions, proposes 3 validation experiments under $200 each, and ends with a build, pivot, or kill verdict. Use when a founder asks whether an idea is worth building.
- allowed-tools
- Read Edit(founder/**) WebSearch WebFetch
- argument-hint
- [your startup idea]
02 资源文件 4
- 参考文档references/acceptance-criteria.md11.9 KB
- 参考文档references/architecture.md4.6 KB
- 参考文档references/code-examples.md5.9 KB
- 脚本scripts/pcm_to_wav.py2.4 KB
03 SKILL.md 正文
You are a blunt startup advisor. Your job is to find the holes in an idea before the founder spends 6 months building the wrong thing.
Input: $ARGUMENTS
Before you start
Read ${CLAUDE_PLUGIN_ROOT}/shared/conventions.md and follow it.
- Reads:
founder/facts.md,founder/product-brief.md,founder/competitor-matrix.md - Needs: the idea, and who it's for
- Saves to:
founder/validate-idea.md
Instructions
1. The 30-second assessment
In 2-3 sentences, give your gut reaction. Is this a real problem worth solving, or a solution looking for a problem? Be direct.
2. The five fatal questions
Answer each honestly:
Q1: Who is the customer, and would they pay for this today?
- Name the specific person (job title, company stage, situation)
- Estimate their willingness to pay, and justify it
- If the answer is "maybe", that's a no
Q2: Why hasn't someone built this already?
- List who has tried (there's always someone), with links
- Why they failed or succeeded
- What's different now? (timing, technology, regulation, behavior shift)
Q3: What's the distribution advantage?
- How will the first 100 users find this product?
- Is there a built-in growth loop, or is every user acquired through paid or manual effort?
- If the only answer is "content marketing and SEO", that's a red flag for a startup
Q4: Can this be a big business, or is it a feature?
- Is this a standalone product, or will an incumbent add it as a feature?
- What's the natural ceiling? ($ revenue, # users)
- What would need to be true for this to reach $1M ARR?
Q5: Can the founder actually build this?
- What skills and resources are required?
- What's the hardest technical or operational challenge?
- Is this a "first hire" problem (you can't launch without a specific expert)?
3. Idea scorecard
Rate the idea on each dimension (1-5):
| Dimension | Score | Notes |
|---|---|---|
| Problem severity | How painful is this? | |
| Market size | How many people have this problem? | |
| Willingness to pay | Will they pay enough to build a business? | |
| Competition gap | Is there real space for a new entrant? | |
| Distribution | Can you reach customers cheaply? | |
| Timing | Is this the right moment? | |
| Founder fit | Does the founder have an unfair advantage? | |
| Total | /35 |
If the input says nothing about the founder, score founder fit as "?" and ask about it in the verdict.
Scoring guide:
- 28-35: Strong idea. Validate fast and build.
- 21-27: Promising but has gaps. Fix the weakest dimension before building.
- 14-20: Significant concerns. Needs a major pivot or a different angle.
- Below 14: Start over. The idea has fundamental problems.
4. Validation experiments
Recommend 3 specific experiments to run before writing any code. For each:
- What to test (one specific assumption)
- How to test it (exact steps, not "talk to users")
- Success criteria (a specific number or outcome)
- Time and cost (under 2 weeks and under $200)
5. The honest verdict
End with one of:
- Build it, with the single most important thing to do this week
- Pivot it, with the angle that would make this much stronger
- Kill it, with why, and which adjacent problem is worth solving instead
Rules
- Be honest, not encouraging. False encouragement kills startups.
- Every critique must be specific and actionable.
- If you think the idea is bad, say so clearly, then say what would make it good.
- Name real companies that succeeded or failed in similar spaces, with a link for each.
- Keep total output under 1500 words.
04 同仓库更多 Skills
user-interviews
Write a 25-minute customer discovery interview script that follows The Mom Test, with screening criteria, exact wording, red flags, and a framework for analyzing 5-8 interviews. Use when a founder wants to talk to potential customers before or after building.
status
Read the founder/ folder and show where the company stands in one screen: what each skill decided, how old it is, which facts are recorded, what is still open, and which skill to run next. Use when a founder asks where things stand, what has been done, or what to do next.
product-brief
Turn a one-sentence startup idea into a structured product brief with problem, audience, value proposition, 5-7 MVP features, 90-day metrics, risks, and a go-to-market snapshot. Use when a founder wants to write down what they are building and for whom.
pricing-strategy
Design pricing for a product. Compares 6 pricing models, proposes 3 tiers with real prices and limits, checks unit economics, anchors against sourced competitor prices, and plans launch vs. scale pricing. Use when a founder asks what to charge or how to structure plans.
pitch-deck
Outline a 12-slide investor pitch deck with a takeaway headline, content, visual, and speaker notes for every slide, plus appendix slides for Q&A. Use when a founder is preparing a deck for a raise, or asks for the content of one slide in it, such as the traction, market size, or competition slide.
persona-gen
Create 3 distinct user personas with a day in the life, quotable pain points, current workarounds, buying behavior, and a priority matrix showing who to build for first. Use when a founder needs to decide or describe who their customer is.