discovery-process

Guide product managers through a structured discovery cycle from problem hypothesis to validated solution.

24|3|Updated Jan 24, 2026
One-click install
npx skills add https://github.com/Prorise-cool/prorise-claude-skills --skill discovery-process-prorise-cool
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: discovery-process
Source: https://github.com/Prorise-cool/prorise-claude-skills/tree/main/.claude/skills/product-specialist/references/domains/product-management/discovery-process
Command: npx skills add https://github.com/Prorise-cool/prorise-claude-skills --skill discovery-process-prorise-cool

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a structured workflow for product managers to systematically explore problem spaces, validate assumptions, and ensure they are solving real customer problems before committing to development.

Core Features & Use Cases

  • End-to-End Discovery: Orchestrates problem framing, customer interviews, synthesis, solution generation, and validation experiments.
  • De-risks Decisions: Reduces the risk of building unwanted features by grounding product decisions in customer evidence.
  • Use Case: When a team has a hypothesis about a user pain point (e.g., "customers struggle with onboarding"), this Skill guides them through the entire process of validating that problem and testing potential solutions.

Quick Start

Initiate the discovery process by framing the problem using the provided problem framing canvas.

Frequently Asked Questions about discovery-process

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is product discovery and how does it validate user problems?

Product discovery is a structured workflow that guides teams from initial problem hypothesis to validated solution. It systematically explores problem spaces and validates assumptions through customer interviews and synthesis to ensure real user problems are solved.

How do I conduct customer interviews for problem validation?

Customer interviews for problem validation are orchestrated within a structured discovery cycle. The process frames the initial problem hypothesis, conducts the interviews, synthesizes the gathered evidence, and builds confidence before committing to full development.

What's the best way to test a product hypothesis before development?

The best way to test a product hypothesis is using a structured discovery process that frames the problem, generates solutions, and runs validation experiments. This reduces the risk of building unwanted features by grounding decisions in customer evidence.

How do I start the product discovery process with a problem hypothesis?

Start the product discovery process by framing your problem hypothesis using a problem framing canvas. This initial step systematically explores the problem space before moving into customer interviews, synthesis, and solution validation experiments.

When do I need a structured process for solution validation?

You need a structured solution validation process when a team has a hypothesis about a user pain point, such as customers struggling with onboarding. It de-risks decisions by validating assumptions and testing potential solutions before committing to development.

Why does product discovery prevent building unwanted features?

Product discovery prevents building unwanted features by systematically validating assumptions and grounding product decisions in customer evidence. This structured workflow avoids the build it and they will come syndrome, ensuring real customer problems are solved.