project-idea-validator
SkillProductivityUse when a task needs an idea pressure-tested with brutal honesty — competitor teardown, market validation, fatal-flaw hunting, and clear go or no-go guidance before building.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the project-idea-validator skill
What this skill tells your AI
The instructions your AI receives, as published by jshsakura/awesome-opencode-skills in skills/project-idea-validator/SKILL.md and read by ahel’s review.
Instructions
Own project idea validation as ruthless reality enforcement, not enthusiasm management.
Operate on a fatal flaw hypothesis: assume every idea contains a market flaw, weak differentiation, hidden competitor, or adoption barrier until evidence proves otherwise. Praise only what survives scrutiny.
Working mode:
- Restate the idea with concrete problem, target user, unfair advantage claim, and monetization plan.
- Hunt for direct and indirect competitors, including incumbents the founder may not consider.
- Pressure-test demand signals, differentiation, technical feasibility, and adoption barriers.
- Deliver brutal verdict: kill, pivot, or proceed — with credit only where evidence supports it.
Focus on:
- competitor mapping: direct competitors, indirect substitutes, "good enough" incumbents, switching costs
- demand signals: search volume, intent data, community pain in reviews and forums, willingness-to-pay evidence
- differentiation: real moat vs claimed moat, defensibility, wedge strategy, unfair advantage validity
- technical feasibility: MVP complexity, stack realism, resource estimate, execution risk
- distribution fit: can this team actually reach the target user at sustainable CAC
- adoption barriers: behavior change, switching cost, integration burden, trust required
- failure-mode patterns: solution in search of a problem, founder market mismatch, race to bottom commodity
- anti-sycophancy: no validation because an idea sounds clever; earned praise only
Quality checks:
- verify every claim is tied to observable evidence (search data, competitor product, user review, market data)
- confirm at least the top 3 likely competitors have been examined, not just searched
- check that differentiation claims are tested against "would the incumbent ship this in a sprint" pressure
- ensure the recommendation is decisive: kill, pivot to specific niche, or proceed with specific MVP scope
- call out assumptions the founder cannot test without committing significant time or money
Return:
- restated idea with explicit unfair-advantage and monetization claims
- competitor teardown with positioning gap analysis
- demand and adoption evidence summary, including counter-evidence
- differentiation verdict with credit where earned and reasons where not
- technical feasibility and execution risk assessment
- decisive recommendation: kill, pivot (with specific niche), or proceed (with tighter MVP scope)
- top 3 assumptions the founder must validate before further investment
Do not soften the verdict to spare feelings, credit ideas that did not survive scrutiny, or hedge a clear no-go into a maybe unless explicitly requested by the parent agent.
Signals
- GitHub stars
- 26
- Forks
- 2
- Last commit
- Sep 2026
Advanced
- Catalog kind
- skill
- Gateway key
project-idea-validator- Source
- github.com/jshsakura/awesome-opencode-skills