product-discovery

Validate product opportunities using OST mapping and structured discovery workflows.

Updated Apr 9, 2026
One-click install
npx skills add https://github.com/Patasse97/claude-skills --skill product-discovery-patasse97
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: product-discovery
Source: https://github.com/Patasse97/claude-skills/tree/main/product-team/product-discovery
Command: npx skills add https://github.com/Patasse97/claude-skills --skill product-discovery-patasse97

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Product teams struggle to validate opportunities and de-risk bets without a structured framework for discovery.

Core Features & Use Cases

  • Structured OST (Opportunity Solution Tree) workflows to map outcomes, opportunities, and solution ideas.
  • Assumption mapping, test planning, and evidence synthesis to de-risk bets.
  • Problem validation interviews, rapid prototyping planning, and discovery sprint templates.

Quick Start

Identify a high-value opportunity and plan a discovery sprint using an OST.

Frequently Asked Questions about product-discovery

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

FAQPage Schema
How do I validate product opportunities and de-risk bets before development?

To validate product opportunities, apply structured discovery workflows using OST-based mapping, assumption prioritization, and problem-solution validation to guide discovery sprints and standardize decision-making.

What is an Opportunity Solution Tree and how does it work for product discovery?

An Opportunity Solution Tree (OST) is a framework to map outcomes, opportunities, and solution ideas. It works by structuring product discovery workflows to connect desired business outcomes directly to the solutions you test.

How do I plan a discovery sprint to test product assumptions?

Plan a discovery sprint by selecting a high-value opportunity, applying assumption mapping to identify testable risks, and using interview templates and experiment scoring to validate problem-solution fit.

Do I need an OST framework to start structured product discovery?

Yes, you need an OST framework. The discovery workflows require an OST framework, interview templates, and experiment scoring matrices to standardize outputs and guide validation effectively.

What's the best way to map assumptions and prioritize solution validation?

The best way to map assumptions is through structured assumption prioritization within a discovery sprint, synthesizing problem validation interviews and rapid prototyping evidence to de-risk solution bets.

When should I not use structured discovery sprints for product validation?

Avoid structured discovery sprints if your team lacks the capacity for problem validation interviews or cannot commit to experiment scoring, as these standardized outputs are required to de-risk bets effectively.