/

/discovery-process

by Dean Petersdeanpeters/product-manager-skills7.1k stars

851

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.

4 files
28.2 KB
Updated 3 months ago
GitHub
No alerts

Ask your Agent

Use this Skill: https://skilld.dev/gh/deanpeters/product-manager-skills/discovery-process

This session only. Nothing lands on disk.

template.md

622 B raw

≈156 tokens on demand. Your agent reads this file only when SKILL.md points to it.

Discovery Process Summary Template

Use this template to capture discovery outputs and decisions.

Template

# Discovery Summary

## Problem Framing
- [Problem statement]
- [Why now]

## Research Insights
- [Top customer pains]
- [Quotes / evidence]
- [Behavioral patterns]

## Personas / JTBD (Optional)
- [Primary persona]
- [Key jobs]

## Opportunities
- [Opportunity 1]
- [Opportunity 2]
- [Opportunity 3]

## Solution Hypotheses
- [Hypothesis 1]
- [Hypothesis 2]

## Experiments Run
- [Experiment + result]

## Decision
- [Go / No-Go / Pivot]

## Next Steps
- [PRD, roadmap, additional discovery]

Source: SKILL.md on GitHub

Third-party checks

No alerts17d4 checks · Risk SAFE

Gen Agent Trust Hub17d
This skill provides a structured workflow for product managers to conduct discovery research, framing problems, and validating solutions. It orchestrates several other component skills to facilitate workshops and interviews. No security issues were detected.
Socket17d
No alerts
Snyk17d
Risk: LOW · No issues
Runlayer6mo
3 files scanned · No issues

Provenance

Signed by skilld at 6a4fbf2. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub last month.

Activeupdated 3 months ago

Capability

argument-hint: [problem hypothesis]
type: workflow
theme: discovery-research

Other metadata

intent: 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.
best_for: [ "Running a full discovery cycle from hypothesis to validated solution", "Investigating a retention or churn problem systematically", "Setting up continuous discovery as an ongoing practice" ]
scenarios: [ "I have a hypothesis that B2B customers struggle with onboarding and want to validate it before building anything", "Our activation rate dropped 15% this quarter and I need to run discovery to find out why" ]
estimated_time: 30-60 min