Agent skill · product strategy · deanpeters
discovery-process
Run a full discovery cycle from problem hypothesis to validated solution. Use when a team needs a structured path through framing, interviews, synthesis, and experiments.
Why this skill is useful
Provides a structured workflow for product discovery that helps validate assumptions and explore problem spaces systematically, which the AI wouldn't generate on its own.
What it needs
About 10k tokens when loaded. Last updated 2026-07-17. 6,302 stars on the source repository.
What this skill does
Purpose Guide product managers through a complete discovery cycle—from initial problem hypothesis to validated solution—by orchestrating problem framing, customer interviews, synthesis, and experimentation skills into a structured process. Use this to systematically explore problem spaces, validate assumptions, and build confidence before committing to full development—avoiding "build it and they will come" syndrome and ensuring you're solving real customer problems. This is not a one-time research project—it's a continuous discovery practice that runs in parallel with delivery, typically 1-2 discovery cycles per quarter. Input Works best with: Your starting problem hypothesis — even a rough one. Also useful: Prior research, customer access, timeline, and what decision the discovery must inform. Anything supplied with the invocation itself — text after the skill name, a pasted context dump, or an appended ARGUMENTS: line — counts as answers already given. Use it and skip whatever it covers; don't re-ask. Arriving empty-handed? That works too. The workflow starts at problem framing and helps you construct the hypothesis first. Example invocation: Run discovery on this hypothesis: SMB admins abandon onboarding because the data-import step requires IT help they don't have. Key Concepts What is the Discovery Process? The discovery process (Teresa Torres, Marty Cagan) is a structured approach to exploring problem spaces and validating solutions before building. It consists of: 1. Frame the Problem — Define what you're investigating and why 2. Conduct Research — Gather qualitative and quantitative evidence 3. Synthesize Insights — Identify patterns, pain points, and opportunities 4. Generate Solutions — Explore multiple solution options 5. Validate Solutions — Test assumptions through experiments 6. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills deanpeters/discovery-process