Agent skill

Product Discovery Process

by deanpeters in deanpeters/Product-Manager-Skills

Guides a product manager through a full discovery cycle from problem hypothesis to validated solution: framing, interviews, synthesis, solution options and experiments.

Custom licenceAuto-check passedProduct & Project Management

Install Product Discovery Process

skills CLI

$ npx skills add deanpeters/Product-Manager-Skills --skill discovery-process -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install deanpeters/Product-Manager-Skills discovery-process --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/deanpeters/Product-Manager-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/discovery-process .claude/skills/discovery-process && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "discovery-process" agent skill from https://github.com/deanpeters/Product-Manager-Skills/tree/main/skills/discovery-process into .claude/skills/discovery-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "discovery-process", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/deanpeters/Product-Manager-Skills/tree/main/skills/discovery-process

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add deanpeters/Product-Manager-Skills --skill discovery-process -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install deanpeters/Product-Manager-Skills discovery-process --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/deanpeters/Product-Manager-Skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/discovery-process .agents/skills/discovery-process && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "discovery-process" agent skill from https://github.com/deanpeters/Product-Manager-Skills/tree/main/skills/discovery-process into .agents/skills/discovery-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "discovery-process", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add deanpeters/Product-Manager-Skills --skill discovery-process -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install deanpeters/Product-Manager-Skills discovery-process --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/deanpeters/Product-Manager-Skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/discovery-process .cursor/skills/discovery-process && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "discovery-process" agent skill from https://github.com/deanpeters/Product-Manager-Skills/tree/main/skills/discovery-process into .cursor/skills/discovery-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "discovery-process", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/deanpeters/Product-Manager-Skills.git --path skills/discovery-process

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add deanpeters/Product-Manager-Skills --skill discovery-process -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install deanpeters/Product-Manager-Skills discovery-process --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/deanpeters/Product-Manager-Skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/discovery-process .gemini/skills/discovery-process && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "discovery-process" agent skill from https://github.com/deanpeters/Product-Manager-Skills/tree/main/skills/discovery-process into .gemini/skills/discovery-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "discovery-process", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install deanpeters/Product-Manager-Skills discovery-process

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add deanpeters/Product-Manager-Skills --skill discovery-process -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/deanpeters/Product-Manager-Skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/discovery-process .github/skills/discovery-process && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "discovery-process" agent skill from https://github.com/deanpeters/Product-Manager-Skills/tree/main/skills/discovery-process into .github/skills/discovery-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "discovery-process", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add deanpeters/Product-Manager-Skills --skill discovery-process -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install deanpeters/Product-Manager-Skills discovery-process --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/deanpeters/Product-Manager-Skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/discovery-process .opencode/skills/discovery-process && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "discovery-process" agent skill from https://github.com/deanpeters/Product-Manager-Skills/tree/main/skills/discovery-process into .opencode/skills/discovery-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "discovery-process", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: discovery-process
GitHub stars: 7.2k
Used in: 1 other repo
Token cost: ~4.9k tokens
SKILL.md length: 1,930 words
Files: 4
Skills in repo: 75
Repo updated: Sep 1, 2026
First seen: Oct 7, 2026
Licence: Custom licence

At a glance

Guides a product manager through a full discovery cycle from problem hypothesis to validated solution: framing, interviews, synthesis, solution options and experiments.

Works in 6 steps: Frame the Problem (Day 1-2) → Research Planning (Day 3) → Conduct Research (Week 1-2) → …
Testing a problem hypothesis before committing to build
SKILL.md covers Purpose, Input, Key Concepts and Application, plus 6 more sections
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

The skill orchestrates problem framing, customer interviews, synthesis and experimentation into one structured process, based on the discovery approach of Teresa Torres and Marty Cagan. The six stages are frame the problem, conduct research, synthesize insights, generate solutions, validate solutions, and decide and document whether to build, pivot or kill. It treats discovery as a continuous practice running alongside delivery, typically one to two cycles per quarter, not a one-time research project.

It works best from a starting problem hypothesis, even a rough one, and anything supplied with the invocation counts as already answered, so it does not re-ask. With no hypothesis it starts at problem framing and helps build one. Bundled files include a template and two sample runs, one of them for life sciences. It lists anti-patterns, such as treating discovery as waterfall research or as user testing. The excerpt is truncated.

When your agent uses it

Testing a problem hypothesis before committing to build
Planning interviews, synthesis and experiments for a new product area
Deciding whether to build, pivot or kill an idea based on evidence

Example prompts

“Run discovery on this hypothesis: new users quit our mobile app because the sign-up form asks for too much.”
“Plan a discovery cycle for a new reporting feature, starting from problem framing.”
“Help me turn my customer interview notes into a build, pivot or kill decision.”

Workflow steps

6 steps, taken from the step headings in SKILL.md.

Frame the Problem (Day 1-2)
Research Planning (Day 3)
Conduct Research (Week 1-2)
Synthesize Insights (End of Week 2)
Generate & Validate Solutions (Week 3)
Decide & Document (End of Week 3-4)

What it can do on your machine

Read from SKILL.md and the folder at commit 1b5a524. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Product Discovery Process loads about 4.9k tokens when it runs. Until then it costs about 47 tokens; SKILL.md has 1,930 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~47
When it runs · the whole SKILL.md, loaded when a task matches: ~4.9k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 1,930 words (~4,851 tokens).

“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…”

— opening of SKILL.md by deanpeters, Custom licence

name: discovery-process
argument-hint: [problem hypothesis]
intent: Guide product managers through a complete discovery cycle—from initial problem hypothesis to validated solution—by orchestrating problem framing, customer…
type: workflow
theme: discovery-research
best_for: Running a full discovery cycle from hypothesis to validated solution, Investigating a retention or churn problem systematically, Setting up continuous…
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…
estimated_time: 30-60 min

Outline of SKILL.md

Purpose
Input
Key Concepts
What is the Discovery Process?
Why This Works
Anti-Patterns (What This Is NOT)
When to Use This
When NOT to Use This
Facilitation Source of Truth
Application
Phase 1: Frame the Problem (Day 1-2)
Activities
Outputs from Phase 1
Decision Point 1: Do we have enough context to start research?
Phase 2: Research Planning (Day 3)
Activities
Outputs from Phase 2
Phase 3: Conduct Research (Week 1-2)
Activities
Outputs from Phase 3
Decision Point 2: Have we reached saturation?
Phase 4: Synthesize Insights (End of Week 2)
Activities
Outputs from Phase 4
Phase 5: Generate & Validate Solutions (Week 3)
Activities
Outputs from Phase 5
Decision Point 3: Did experiments validate solution?
Phase 6: Decide & Document (End of Week 3-4)
Activities

Read the full SKILL.md on GitHub

Files

SKILL.md and 3 other files in skills/discovery-process of deanpeters/Product-Manager-Skills.

SKILL.md
examples/sample-lifesciences.md
examples/sample.md
template.md

Open the folder on GitHubat commit 1b5a524

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in deanpeters/Product-Manager-Skills, which our catalogue first saw on October 7, 2026.

getcrew44/crew44daemon/internal/presets/defaultcrew/skills/product/discovery-process

Compare with similar skills

Product Discovery Process next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Product Discovery Process compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Product Discovery Process this skilldeanpeters/Product-Manager-Skills	7.2k	1 repos	~4.9k	Automated safety check: Pass	Custom licence	1 mo ago
Opportunity Solution Treeavelikiy/great_cto	102	—	~1.8k	Automated safety check: Pass	MIT	today
Gingiris User InterviewGingiris-1031/Competitor-analysis-tool	110	—	~1.2k	Automated safety check: Pass	None	yesterday
Product Discoverymajiayu000/spellbook	287	—	~3.3k	Automated safety check: Pass	MIT	yesterday
Inspired Productwondelai/skills	2.4k	—	~4k	Automated safety check: Pass	MIT	29 days ago
Mom Testwondelai/skills	2.4k	—	~4.2k	Automated safety check: Pass	MIT	29 days ago

Similar skills

Opportunity Solution Tree
avelikiy/great_cto
Builds an Opportunity Solution Tree that links one measurable outcome to customer opportunities, candidate solutions and experiments.
102 GitHub stars~1.8k tokensUpdated today
Product & Project ManagementAuto-check passed
Gingiris User Interview
Gingiris-1031/Competitor-analysis-tool
🇺🇸 User Interview & Cold-Start Operations Playbook — Battle-tested framework from HeyGen's 937 interviews to PMF.
110 GitHub stars~1.2k tokensUpdated yesterday
Product & Project ManagementAuto-check passed
Product Discovery
majiayu000/spellbook
Product discovery and market research expert. An agent skill from majiayu000/spellbook.
287 GitHub stars~3.3k tokensUpdated yesterday
Product & Project ManagementAuto-check passed
Inspired Product
wondelai/skills
Build empowered product teams using discovery and delivery dual-track.
2.4k GitHub stars~4k tokensUpdated 29 days ago
Product & Project ManagementAuto-check passed
Mom Test
wondelai/skills
Talk to customers without leading them using Mom Test rules: discuss their life not your idea, ask about specifics in the past, and talk less.
2.4k GitHub stars~4.2k tokensUpdated 29 days ago
Product & Project ManagementAuto-check passed
Product Manager Toolkit
borghei/Claude-Skills
Product manager toolkit covering RICE prioritization, customer interview analysis, PRDs, and discovery frameworks.
891 GitHub stars~5.8k tokensUpdated 2 days ago
Product & Project ManagementAuto-check passed

Questions about Product Discovery Process

What does Product Discovery Process do?

Guides a product manager through a full discovery cycle from problem hypothesis to validated solution: framing, interviews, synthesis, solution options and experiments. The skill orchestrates problem framing, customer interviews, synthesis and experimentation into one structured process, based on the discovery approach of Teresa Torres and Marty Cagan. The six stages are frame the problem, conduct research, synthesize insights, generate solutions, validate solutions, and decide and document whether to build, pivot or kill.

When should I use Product Discovery Process?

Product Discovery Process fits situations like: testing a problem hypothesis before committing to build; planning interviews, synthesis and experiments for a new product area; deciding whether to build, pivot or kill an idea based on evidence.

How do I install Product Discovery Process in Claude Code?

Run `npx skills add deanpeters/Product-Manager-Skills --skill discovery-process -a claude-code`. Or copy the skill folder (skills/discovery-process in deanpeters/Product-Manager-Skills) into .claude/skills/discovery-process in your project. Claude Code loads it when a task matches its description.

How do I install Product Discovery Process in Codex?

Run `npx skills add deanpeters/Product-Manager-Skills --skill discovery-process -a codex`. Or copy the skill folder (skills/discovery-process in deanpeters/Product-Manager-Skills) into .agents/skills/discovery-process in your project. Codex loads it when a task matches its description.

Can I use Product Discovery Process in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add deanpeters/Product-Manager-Skills --skill discovery-process -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/discovery-process, .gemini/skills/discovery-process, .github/skills/discovery-process and .opencode/skills/discovery-process in your project.

What does Product Discovery Process need to run?

SKILL.md names no scripts, command-line tools or credentials: Product Discovery Process is instructions for the agent only.

Does Product Discovery Process access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Product Discovery Process safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Product Discovery Process use?

Product Discovery Process has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.

How many tokens does Product Discovery Process use?

About 4.9k tokens (SKILL.md is roughly 19k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Product Discovery Process?

Skills that share tags, products or a category with Product Discovery Process: Opportunity Solution Tree (avelikiy/great_cto, 102 stars), Gingiris User Interview (Gingiris-1031/Competitor-analysis-tool, 110 stars), Product Discovery (majiayu000/spellbook, 287 stars) and Inspired Product (wondelai/skills, 2.4k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Product Discovery Process?

deanpeters (a GitHub user) maintains it in deanpeters/Product-Manager-Skills, which has 7,224 GitHub stars. The repository holds 75 skills in this directory. The repository was last updated on September 1, 2026.

Source: deanpeters/Product-Manager-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Product Discovery Process

Install Product Discovery Process

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Files

Used in 1 other repository

Compare with similar skills

Similar skills

Opportunity Solution Tree

Gingiris User Interview