Product discovery and validation process
This skill inherits all available tools. When active, it can use any tool Claude has access to.
Product discovery is the process of understanding user problems and validating solutions before building.
Understand → Explore → Validate → Define
Activities:
Questions to Answer:
Output:
Activities:
Questions to Answer:
Output:
Activities:
Questions to Answer:
Output:
Activities:
Output:
## Problem Statement
**User**: [Who experiences this problem]
**Problem**: [What they're trying to do]
**Current State**: [How they do it today]
**Pain Points**: [What makes it painful]
**Impact**: [What happens if unsolved]
## Hypothesis
We believe that [solution]
for [user segment]
will result in [outcome]
We will know this is true when:
- [Measurable signal 1]
- [Measurable signal 2]
## Interview Guide: [Topic]
### Opening (5 min)
- Thank them for their time
- Explain purpose (learning, not selling)
- Ask permission to take notes
### Context (10 min)
- Tell me about your role
- Walk me through a typical [relevant activity]
- What tools do you use for [topic]?
### Problem Exploration (20 min)
- What's the hardest part about [topic]?
- Tell me about the last time you [experienced problem]
- How did you handle it?
- What did you try first?
### Solution Exploration (10 min)
- If you could wave a magic wand, what would change?
- Have you tried [alternative]? What happened?
- What would make you switch from current solution?
### Closing (5 min)
- Is there anything I should have asked?
- Can I follow up if I have more questions?
"We already know what to build"
"Users asked for X, let's build X"
"I have a great idea for..."
"We need more research"
Discovery is complete when you can confidently answer: