discovery-process

Orchestrates a six-phase product discovery cycle from problem hypothesis to validated solution decision.

1|1|Updated Jul 6, 2026
One-click install
npx skills add https://github.com/muhammaddadu/ai-skill-collection --skill discovery-process-muhammaddadu
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: discovery-process
Source: https://github.com/muhammaddadu/ai-skill-collection/tree/main/2-discovery/discovery-process
Command: npx skills add https://github.com/muhammaddadu/ai-skill-collection --skill discovery-process-muhammaddadu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Product teams often build features based on untested assumptions, wasting months of engineering effort on solutions nobody wants. This Skill provides a structured 2-4 week discovery workflow that validates problems and solutions through customer interviews, synthesis, and experiments before committing to delivery. ## Core Features & Use Cases - Six-Phase Workflow: Guides teams through problem framing, research planning, customer interviews, insight synthesis, solution validation, and go/no-go decisions with clear decision gates. - Skill Orchestration: Coordinates 10+ component skills including problem-framing-canvas, discovery-interview-prep, opportunity-solution-tree, and prd-development into one coherent process. - Use Case: Your activation rate dropped 15% this quarter. Use this Skill to frame the problem hypothesis, interview 5-10 churned customers, synthesize pain points via affinity mapping, test a prototype solution, and produce a validated discovery brief with a go/no-go recommendation. ## Quick Start Run the discovery process to investigate why our onboarding completion rate dropped, starting with problem framing and ending with a validated go/no-go decision brief.

Frequently Asked Questions about discovery-process

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

FAQPage Schema
How do I run a product discovery process from hypothesis to validation?▼

Follow six phases: frame the problem with a problem-framing canvas, plan and recruit for 5-10 customer interviews, conduct research using Mom Test questions, synthesize insights via affinity mapping, generate and test solutions with experiments, then make a documented go/no-go decision.

How many customer interviews are needed for product discovery?▼

Interview 5-10 customers per discovery cycle, continuing until saturation—when the same pain points emerge across three or more interviews with no new insights. Teresa Torres recommends continuous discovery with one customer interview per week.

What is the difference between product discovery and user testing?▼

Discovery validates whether a problem exists and is worth solving before building, while user testing validates whether a specific solution works. Discovery runs continuously alongside delivery rather than as a one-time research phase.

When should I not use a discovery process?▼

Skip discovery for well-understood problems ready for execution, tactical bug fixes, or technical debt. Also address stakeholder alignment first if a solution has already been committed to, since discovery assumes an open problem space.

How long does a product discovery cycle take?▼

A fast track takes 3 weeks with 5 interviews and one experiment, a typical cycle takes 4 weeks with 7-10 interviews, and thorough discovery runs 6-8 weeks. Time-box discovery to avoid analysis paralysis and move to execution after the decision phase.