$npx -y skills add ncklrs/startup-os-skills --skill product-discoveryExpert product discovery guidance for user research and problem validation. Use when conducting user interviews, validating problems, applying jobs-to-be-done framework, sizing opportunities, customer segmentation, competitive analysis, prototype testing, usability testing, desig
| 1 | # Product Discovery |
| 2 | |
| 3 | Strategic user research and problem validation expertise — from interview techniques and JTBD to opportunity sizing and insight synthesis. |
| 4 | |
| 5 | ## Philosophy |
| 6 | |
| 7 | Great products start with great problems. Discovery is how you find problems worth solving for people who will pay. |
| 8 | |
| 9 | The best product discovery: |
| 10 | 1. **Talk to users, not stakeholders** — Customers know their problems, not solutions |
| 11 | 2. **Validate problems before solutions** — Build the right thing, then build it right |
| 12 | 3. **Quantify and qualify** — Numbers tell you what, conversations tell you why |
| 13 | 4. **Continuous over batched** — Weekly habits beat quarterly projects |
| 14 | |
| 15 | ## How This Skill Works |
| 16 | |
| 17 | When invoked, apply the guidelines in `rules/` organized by: |
| 18 | |
| 19 | - `research-*` — User interview techniques, survey design, research ops |
| 20 | - `discovery-*` — Problem discovery, JTBD framework, validation |
| 21 | - `analysis-*` — Synthesis, segmentation, competitive analysis |
| 22 | - `testing-*` — Prototype testing, usability testing |
| 23 | |
| 24 | ## Core Frameworks |
| 25 | |
| 26 | ### Discovery Process |
| 27 | |
| 28 | | Phase | Activities | Outputs | |
| 29 | |-------|------------|---------| |
| 30 | | **Explore** | Interviews, observation, data mining | Problem space map | |
| 31 | | **Validate** | Problem interviews, surveys, experiments | Validated problems | |
| 32 | | **Prioritize** | Opportunity scoring, segmentation | Prioritized roadmap | |
| 33 | | **Test** | Prototype testing, usability studies | Solution validation | |
| 34 | |
| 35 | ### Jobs-to-be-Done Framework |
| 36 | |
| 37 | ``` |
| 38 | ┌─────────────────────┐ |
| 39 | │ FUNCTIONAL JOB │ |
| 40 | │ (What they do) │ |
| 41 | └──────────┬──────────┘ |
| 42 | │ |
| 43 | ┌────────────────┼────────────────┐ |
| 44 | │ │ │ |
| 45 | ▼ ▼ ▼ |
| 46 | ┌──────────┐ ┌──────────┐ ┌──────────┐ |
| 47 | │ EMOTIONAL│ │ SOCIAL │ │ CONTEXT │ |
| 48 | │ JOB │ │ JOB │ │ (When/ │ |
| 49 | │ (Feel) │ │ (Appear) │ │ Where) │ |
| 50 | └──────────┘ └──────────┘ └──────────┘ |
| 51 | ``` |
| 52 | |
| 53 | ### Opportunity Scoring (OST) |
| 54 | |
| 55 | | Factor | Weight | Description | |
| 56 | |--------|--------|-------------| |
| 57 | | **Importance** | 40% | How important is this job to the customer? | |
| 58 | | **Satisfaction** | 30% | How satisfied are they with current solutions? | |
| 59 | | **Frequency** | 20% | How often do they encounter this problem? | |
| 60 | | **Willingness to Pay** | 10% | Will they pay to solve this? | |
| 61 | |
| 62 | **Opportunity Score = Importance + max(Importance - Satisfaction, 0)** |
| 63 | |
| 64 | ### Research Method Selection |
| 65 | |
| 66 | ``` |
| 67 | ┌─────────────────────────────────────────────────────────────┐ |
| 68 | │ GENERATIVE RESEARCH │ |
| 69 | │ (Discover unknown unknowns) │ |
| 70 | │ ┌───────────┐ ┌───────────┐ ┌───────────┐ │ |
| 71 | │ │Contextual │ │ Discovery │ │ Diary │ │ |
| 72 | │ │ Inquiry │ │ Interviews│ │ Studies │ │ |
| 73 | │ └───────────┘ └───────────┘ └───────────┘ │ |
| 74 | ├─────────────────────────────────────────────────────────────┤ |
| 75 | │ EVALUATIVE RESEARCH │ |
| 76 | │ (Validate known hypotheses) │ |
| 77 | │ ┌───────────┐ ┌───────────┐ ┌───────────┐ │ |
| 78 | │ │ Usability │ │ A/B │ │ Prototype │ │ |
| 79 | │ │ Testing │ │ Testing │ │ Testing │ │ |
| 80 | │ └───────────┘ └───────────┘ └───────────┘ │ |
| 81 | ├─────────────────────────────────────────────────────────────┤ |
| 82 | │ QUANTITATIVE RESEARCH │ |
| 83 | │ (Measure and prioritize) │ |
| 84 | │ ┌───────────┐ ┌───────────┐ ┌───────────┐ │ |
| 85 | │ │ Surveys │ │ Analytics │ │ Card │ │ |
| 86 | │ │ │ │ Review │ │ Sorting │ │ |
| 87 | │ └───────────┘ └───────────┘ └───────────┘ │ |
| 88 | └─────────────────────────────────────────────────────────────┘ |
| 89 | ``` |
| 90 | |
| 91 | ### Customer Segmentation Matrix |
| 92 | |
| 93 | | Dimension | Consumer (B2C) | Business (B2B) | |
| 94 | |-----------|----------------|----------------| |
| 95 | | **Demographics** | Age, income, location | Company size, industry, revenue | |
| 96 | | **Behavior** | Usage patterns, purchase history | Buying process, tech stack | |
| 97 | | **Psychographics** | Values, lifestyle, attitudes | Company culture, risk tolerance | |
| 98 | | **Needs** | Problems, goals, aspirations | Business outcomes, KPIs | |
| 99 | |
| 100 | ### Continuous Discovery Cadence |
| 101 | |
| 102 | ``` |
| 103 | Weekly: |
| 104 | ├── 2-3 customer interviews |
| 105 | ├── Review analytics/feedback |
| 106 | └── Update opportunity backlog |
| 107 | |
| 108 | Monthly: |
| 109 | ├ |