Behavior led validation
Skill eltntawy/idea-discovery-playbook/skills/behavior-led-validation
16 agent skills to validate software ideas before you build — Mom Test interviews, JTBD, market research, pretotype tests, unit economics, and go/no-go scorecards. For Cursor, Claude Code & skills.sh.
npx -y skills add eltntawy/idea-discovery-playbook --skill behavior-led-validationAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Orchestrates behavior-led idea and market validation—problem interviews, pretotype experiments, paid traffic, demand proxies, competitor revenue estimates, and unit economics—before build. Use when validating a business idea end-to-end, testing willingness to pay, or planning experiments before build.
SKILL.md
4.5 KB, as published. Nobody here has run it
Behavior-Led Validation
Orchestrator skill. For depth on one step, invoke the child skill listed below. For stage gates and artifact order, start with discovery-playbook.
Principle
Validate with observed behavior and payment, not opinions. Strongest signal: customers pay at the target price before software exists.
Validation order: idea validation → market validation → product validation (after a prototype). Landing pages, ad tests, and concierge delivery are not product validation.
Workspace rules
- No-build boundary: no production app scaffold until
idea-scorecardrecords Strong go or Conditional go. - Read
discovery/INDEX.mdand onlydiscovery/<topic-slug>/before extending work. Creatediscovery/INDEX.mdif missing. - Do not open
discovery/archive/unless the user explicitly asks.
Phase map
| Phase | Goal | Primary skills |
|---|---|---|
| Idea | Problem is real and painful | assumption-map, problem-discovery, regulatory-risk-scan (if regulated), feasibility-gate |
| Market | Demand, wedge, economics | market-research, competitor-landscape, market-sizing, positioning-wedge, revenue-model |
| Demand test | Falsify riskiest assumptions | validation-experiments |
| Decision | Go / conditional / pivot / kill | idea-scorecard, discovery-synthesis |
| Product (post-prototype) | Solution fit | pmf-sean-ellis |
Phase 1 — Idea and market demand (summary)
- Problem interviews — follow
problem-discovery(15–20 ICP, Mom Test ladder, commitments). Optional switching depth →jtbd-interviews. - Willingness to pay — priced landing + Stripe or equivalent; thresholds in
validation-experiments. Not validated: email-only waitlist. - Paid traffic — ~$100–$500; track CTR and conversion; compute ILI when applicable (see
validation-experiments). - Desk demand — keywords and forums as research priority proxies only; pair with payment or interviews.
Save under discovery/<topic-slug>/briefs/, research/, or experiments/.
Phase 2 — Revenue and costs (summary)
- Competitor revenue: headcount heuristic, mobile estimates, aggregators — label all as assumptions.
- Unit economics: LTV:CAC ≥ 3:1 for strong go; < 2:1 kill — see
revenue-modelbands. - Reference metric bands (directional, verify for segment): seed MRR narratives, B2B retention, NPS — not pass/fail without context.
Full scenarios → revenue-model.
Evidence mapping
Use the canonical hierarchy in idea-scorecard (levels 1–5). Quick reference:
| Label | Maps to level |
|---|---|
| L0–L1 views, likes, compliments | 1–2 |
| L2 waitlist / signup | 3 |
| L3 repeat use, design-partner time | 4 |
| L4 deposit, LOI, pilot | 5 |
| L5 recurring payment at target price | 5 |
Strong go still requires the weighted scorecard bar in idea-scorecard.
Strongest path
When feasible: concierge MVP for a small paid cohort, then automate. Sequence with fake door → concierge per validation-experiments.
Regulated ideas
If health, fintech, legal, or similar constraints apply → regulatory-risk-scan before scaling tests.
Output checklist
- State validation phase and riskiest assumption
- List child skills invoked or planned
- Facts / Assumptions / Evidence / Analysis / Decision / Next experiment
- Update
discovery/INDEX.mdwhen opening or archiving a topic