pm-discovery

Plans and critiques product discovery processes matched to decision risk and evidence needs.

12|2|Updated Jun 22, 2026
One-click install
npx skills add https://github.com/Uxcel-Lab/product-skills --skill pm-discovery-uxcel-lab
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pm-discovery
Source: https://github.com/Uxcel-Lab/product-skills/tree/main/pm/processes/discovery
Command: npx skills add https://github.com/Uxcel-Lab/product-skills --skill pm-discovery-uxcel-lab

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams often treat discovery as a one-time research phase, jump straight to building features from requests, or run generic research plans that don't match the stakes of the decision. This Skill structures product discovery so it is continuous, problem-first, outcome-oriented, and proportionate to the risk being retired. ## Core Features & Use Cases - Risk-First Framing: Identifies which of the four risks (value, usability, feasibility, business viability) is most uncertain and calibrates how much certainty the decision requires before committing. - Always-Apply Core Rules: Enforces continuous discovery cadence, outcomes over output, problem-before-solution validation, past-behavior interviewing (the Mom Test), evidence matched to risk, and ethical inclusive research. - Context-Dependent Trade-offs: Surfaces decisions like qualitative vs. quantitative, lightweight vs. deep study, and DIY vs. specialist research with explicit trade-offs rather than auto-applying one approach. - Use Case: A PM asked to "figure out what to build" for a new retention initiative uses this Skill to validate the underlying problem through customer interviews, define a measurable product outcome, and only then generate and compare solution hypotheses. ## Quick Start Ask the assistant to plan a product discovery process for your next initiative, stating which risk you need to de-risk and how reversible the decision is.

Frequently Asked Questions about pm-discovery

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

FAQPage Schema
How do I plan a product discovery process?▼

Start by naming which risk is most uncertain: value, usability, feasibility, or business viability. Then match research methods to how reversible and expensive the decision is, keeping discovery continuous rather than a one-time phase.

What is continuous discovery in product management?▼

Continuous discovery is a weekly habit of lightweight customer contact, such as short interviews, support-ticket reviews, and sales call observation, instead of a single upfront research phase. Automating recruiting with booking links or in-product intercepts keeps the habit alive during busy sprints.

How do I choose between qualitative and quantitative user research?▼

Use qualitative methods like interviews to understand why and get early signal, and quantitative methods like analytics to confirm what is happening at scale. Cross-check both; when they conflict, run another test before committing to a decision.

Why do user interviews produce misleading answers?▼

Asking hypothetical questions like "would you use this?" produces polite false positives. Ask about past behavior instead, such as "walk me through the last time you faced this problem," which yields verifiable specifics rather than guesses about the future.

When should I stop researching and commit to a build decision?▼

Commit when you have bought exactly the certainty the decision needs based on its risk and reversibility. Over-researching a cheap reversible tweak wastes time, while under-researching an irreversible costly bet leads to shipping the wrong thing.