discovery-process — Claude Code skill: what it does, how to install
Structures product discovery from an initial assumption to tested solutions so teams build features based on verified customer needs.
npx skills add deanpeters/Product-Manager-Skills --skill discovery-process -a claude-codeWhat discovery-process does
This skill guides product managers through customer discovery before engineering work begins. Grounded in principles from Teresa Torres and Marty Cagan, it splits the research effort into six distinct phases. The full path spans two to four weeks, while an initial framing pass takes about 30 to 60 minutes.
The agent structures problem framing, persona definitions, and Jobs-to-be-Done mapping. It asks one prompt at a time. This allows you to construct hypotheses even with minimal background context. You can also paste support notes or user feedback directly into the prompt to skip earlier diagnostic questions.
Discovery adds unnecessary friction when fixing clear software bugs or handling predefined scope. Use this workflow when investigating sharp activation drops or evaluating strategic concepts before committing roadmap capacity.
What it helps with
- frame a clear hypothesis around an unverified customer pain point
- diagnose quarterly drops in user retention or activation metrics
- prepare structured interview questions for target user segments
- map customer motivations through Jobs-to-be-Done frameworks
- evaluate solution options with lightweight experiments before development
Example prompts for the agent
- Run discovery on hypothesis: team leads abandon setup because file migration requires admin rights.
- Help me investigate why user activation dropped by 15% this quarter.
- Draft a problem framing canvas for our planned self-service billing workflow.
How to install discovery-process
1Skills CLI (Vercel)
npx skills add deanpeters/Product-Manager-Skills --skill discovery-process -a claude-code2Manually: put the files in place
~/.claude/skills/discovery-process/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/discovery-process/
1Skills CLI (Vercel)
npx skills add deanpeters/Product-Manager-Skills --skill discovery-process -a codex2Manually: put the files in place
.agents/skills/discovery-process/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add deanpeters/Product-Manager-Skills --skill discovery-process -a cursor2Manually: put the files in place
.cursor/skills/discovery-process/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install deanpeters/Product-Manager-Skills discovery-process2Manually: put the files in place
.github/skills/discovery-process/SKILL.md1Skills CLI (Vercel)
npx skills add deanpeters/Product-Manager-Skills --skill discovery-process -a gemini-cli2Platform CLI
gemini skills install https://github.com/deanpeters/Product-Manager-Skills --path skills/discovery-processManually: put the files in place
.devin/skills/discovery-process/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add deanpeters/Product-Manager-Skills --skill discovery-process -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
From the same set7
The whole set →Similar
Questions about discovery-process
How do I install discovery-process in Claude Code?
Run npx skills add deanpeters/Product-Manager-Skills --skill discovery-process -a claude-code in your terminal. This saves the skill configuration to ~/.claude/skills/discovery-process/SKILL.md.
What does the discovery-process skill do?
It turns open-ended product questions into a six-phase investigation workflow. The skill guides framing, qualitative research, synthesis, and solution tests before teams write production code.
When should this discovery workflow be skipped?
Skip it for straightforward bug fixes, technical debt work, or initiatives where stakeholders have already locked in a specific implementation. It helps most when root causes and user behaviors remain uncertain.