Product Discovery
Use when validating product opportunities, mapping assumptions, planning discovery sprints, or testing problem-solution fit before committing delivery resources.
Before & after
Same prompt, same agent — the only difference is the skill.
Product discovery is a structured way to validate assumptions before you build. You could talk to potential customers to understand their problems, then test whether your proposed solution actually solves them. It's helpful to document your key assumptions upfront — who the customer is, what problem they have, how big the problem is — then design conversations or experiments to test each assumption. You might do customer interviews, surveys, or even a landing page test. The goal is to get evidence that people would actually pay for your solution. What's your initial hypothesis about who your customer is and what problem you're solving?
DISCOVERY SPRINT PLAN (3 weeks) WEEK 1: ASSUMPTION MAPPING Assumption 1: ICP is technical founders, ages 28-40, building SaaS Assumption 2: Pain point is onboarding complexity (estimated cost $50K/year per company) Assumption 3: Willingness to pay: $500-2000/month Assumption 4: Main competitor is in-house solution, not point tools WEEK 2: CUSTOMER INTERVIEWS (12 interviews) → Recruit: 3 failed founders, 4 current founder/CEOs, 5 engineering leads → Question arc: Current process (15 min) → Problem depth (15 min) → Solution reaction (10 min) → Output: Transcripts + synthesis of top 3 pain points + buyer readiness score WEEK 3: LANDING PAGE TEST → Build simple one-pager describing solution (no product) → Drive 200-300 visitors via paid ads ($500 budget) → Measure: Conversion rate target 5-8% email signup → If below 3%, concept fails validation DECISION GATE Green light → Proceed to MVP: All 3 assumptions validated, 60%+ interviewees said they'd try it Red light → Pivot or abandon: High contradiction in interviews, landing page converts below 2% Yellow light → Iterate discovery: Assumption 2 strong but 1 and 3 weak, refocus interviews OUTPUT DELIVERABLES • Cleaned interview recordings (anonymized) • Assumption validation matrix (yes/no/partial per assumption) • 1-pager: top 5 findings and recommendation
About this skill
name: product-discovery description: Use when Use when validating product opportunities, mapping assumptions, planning discovery sprints, or testing problem-solution fit before committing delivery resources.
Product Discovery
Use when validating product opportunities, mapping assumptions, planning discovery sprints, or testing problem-solution fit before committing delivery resources.
What you get
- Public GitHub repo (alirezarezvani/claude-skills)
- the product-discovery skill folder with SKILL.md. Part of a 337-skill / 30-agent / 70-command install.
Customize your output
- Fork the repo and adapt the skill's instructions and references to your workflow.
Example output
Activates automatically when your request matches Product Discovery; chains with the other skills, agents, and commands in the collection.
Best for
Creators, builders, and teams using Claude Code.
SKILL.md preview
---
name: product-discovery
description: Use this skill when validating product opportunities, mapping assumptions, planning discovery sprints, or testing problem-solution fit before committing delivery resources.
version: 1.0.0
category: Business & Ops / Product
author: AgentVolt
license: proprietary
tags:
- business-ops
- product
---
# Product Discovery
Runs structured discovery before a team commits engineering time: mapping what's assumed versus known, and designing the smallest test that would prove or kill the idea.
## When to use
… (sign up to view the full skill)More business & ops skills
View all Business & Ops skills →Product Manager Toolkit
Comprehensive toolkit for product managers including RICE prioritization, customer interview analysis, PRD templates, discovery frameworks, and go-to-market strategies.
Product Skills
Coordinates a set of product-management sub-skills — prioritization, discovery, UX research, competitive teardown, analytics, roadmapping.
Experiment Designer
Use when planning product experiments, writing testable hypotheses, estimating sample size, prioritizing tests, or interpreting A/B outcomes with practical statistical rigor.
UX Researcher & Designer
UX research and design toolkit for Senior UX Designer/Researcher including data-driven persona generation, journey mapping, usability testing frameworks, and research synthesis.