Individual skill
idea-validation
Help users de-risk new product bets by testing core assumptions, building low-fidelity prototypes, and gathering high-signal evidence before investing heavy engineering resources.
skills/idea-validation/SKILL.md
Source commit 13598cc54e09399bc1bc1398b0fca284110efb2f
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Instructions only
- Last checked
- Nov 9, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 1,478
- Repository last updated
- Jul 16, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- ai-agents Repository topic
- ai-assistant Repository topic
- claude Repository topic
- claude-code Repository topic
- lenny-rachitsky Repository topic
- llm Repository topic
- pm-tools Repository topic
- product-management Repository topic
- skills Repository topic
- product-skills Repository topic
- engineering Derived category
- testing Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 6,123 bytesreferences/artifacts.mddoc · 44,357 bytesreferences/guest-insights.mddoc · 35,274 bytes
Read excerpt
# Idea Validation
Stop building things people don't want by moving from opinion to evidence-based development.
Help the user with idea validation using insights from 31 guests and posts across Lenny's Podcast and Newsletter.
## How to Help
1. **Clarify the Core Hypothesis** - Help the user define the specific problem, target audience, and the most 'risky' assumptions using the Founding Hypothesis Scorecard.
2. **Select a Validation Path** - Guide the user through choosing between the 'Listening Path', 'Manual Path', or 'Self-Serve Path' based on their proximity to the problem.
3. **Design Low-Fidelity Experiments** - Recommend specific 'Wizard of Oz' or 'Fake Door' tests to simulate the solution without building a backend.
4. **Evaluate Signal Quality** - Help users distinguish between polite interest and real market pull by looking for financial commitment or high-effort usage.
## Core Principles