SkillAgentSearch skills...

discovery-process

Run a full discovery cycle from problem hypothesis to validated solution

Install / Use

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

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

92/100

Supported Platforms

Universal

Tags

Our assessment of discovery-process

discovery-process scores 92/100 on our quality scale, 12th of 61 Product Management skills we index (top 20%).

Its SKILL.md is 19 KB long, well organised into 43 sections with 2 code examples: a thorough specification that gives an agent plenty to work with.

With 7,063 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
30/30
Structure
18/20
Description
12/15
Adoption
16/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 3 months ago, so discovery-process is actively maintained.
  • Our last check on 2026-10-05 found the source still online.
  • No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
  • Its trust signals score 88/100, with 1 caution from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-09-26. Automated pattern scan on 2026-09-26. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

discovery-process compared with similar skills

All 4 of these similar skills score higher than discovery-process; compare them before choosing.

SkillScoreStarsUpdatedFormat
discovery-process (this skill)by deanpeters927.1k3mo agoSKILL.md
x402by browser-use100121.0k3d agoSKILL.md
algorithmic-artby anthropics100177.9k55d agoSKILL.md
pptxby anthropics100177.9k55d agoSKILL.md
designby nextlevelbuilder100149.0k6d agoSKILL.md

Frequently asked questions

How do I install discovery-process?
Run npx skills add deanpeters/Product-Manager-Skills --skill discovery-process. The install tabs above show the steps for each supported agent.
Which AI agents does discovery-process work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is discovery-process safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It declares no license and scores 88/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is discovery-process still maintained?
The repository was last updated about 3 months ago, so discovery-process is actively maintained.

name: discovery-process argument-hint: "[problem hypothesis]" description: 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. 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. 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 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"

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. Decide & Document — Commit to build, pivot, or kill

Why This Works

  • De-risks product decisions: Tests assumptions before expensive builds
  • Customer-centric: Grounds decisions in real customer problems, not internal opinions
  • Iterative: Builds confidence progressively through small experiments
  • Fast learning: Discovers "no-go" signals early, saves wasted effort

Anti-Patterns (What This Is NOT)

  • Not waterfall research: Discovery runs continuously, not once before dev
  • Not user testing: Discovery validates problems; testing validates solutions
  • Not a substitute for shipping: Discovery informs delivery, doesn't replace it

When to Use This

  • Exploring new product/feature areas
  • Investigating retention or churn problems
  • Validating strategic initiatives before roadmap commitment
  • Continuous discovery (weekly customer touchpoints)

When NOT to Use This

  • For well-understood problems (move to execution)
  • When stakeholders have already committed to a solution (address alignment first)
  • For tactical bug fixes or technical debt (no discovery needed)

Facilitation Source of Truth

When running this workflow as a guided conversation, use workshop-facilitation as the interaction protocol.

It defines:

  • session heads-up + entry mode (Guided, Context dump, Best guess)
  • one-question turns with plain-language prompts
  • progress labels (for example, Context Qx/8 and Scoring Qx/5)
  • interruption handling and pause/resume behavior
  • numbered recommendations at decision points
  • quick-select numbered response options for regular questions (include Other (specify) when useful)

This file defines the workflow sequence and domain-specific outputs. If there is a conflict, follow this file's workflow logic.

Application

Use template.md for the full fill-in structure.

This workflow orchestrates 6 phases over 2-4 weeks, using multiple component and interactive skills.


Phase 1: Frame the Problem (Day 1-2)

Goal: Define what you're investigating, who's affected, and success criteria.

Activities

1. Run Problem Framing Canvas

  • Use: skills/problem-framing-canvas/SKILL.md (interactive - MITRE)
  • Participants: PM, design, engineering lead
  • Duration: 120 minutes
  • Output: Problem statement + "How Might We" question

2. Create Formal Problem Statement

  • Use: skills/problem-statement/SKILL.md (component)
  • Participants: PM
  • Duration: 30 minutes
  • Output: Structured problem statement with hypothesis

3. Define Proto-Personas (If Needed)

  • Use: skills/proto-persona/SKILL.md (component)
  • When: If target customer segment is unclear
  • Duration: 60 minutes
  • Output: Hypothesis-driven personas

4. Map Jobs-to-be-Done (If Needed)

  • Use: skills/jobs-to-be-done/SKILL.md (component)
  • When: If customer motivations are unclear
  • Duration: 60 minutes
  • Output: JTBD statements

Outputs from Phase 1

  • Problem hypothesis: "We believe [persona] struggles with [problem] because [root cause], leading to [consequence]."
  • Research questions: 3-5 questions to answer through discovery
  • Success criteria: What would validate/invalidate the problem?

Decision Point 1: Do we have enough context to start research?

If YES: Proceed to Phase 2 (Research Planning)

If NO: Gather existing data first:

  • Review support tickets, churn surveys, NPS feedback
  • Analyze product analytics (drop-off points, usage patterns)
  • Review competitor research, market trends
  • Time impact: +2-3 days

Phase 2: Research Planning (Day 3)

Goal: Design research approach, recruit participants, prepare interview guide.

Activities

1. Prep Discovery Interviews

  • Use: skills/discovery-interview-prep/SKILL.md (interactive)
  • Participants: PM, design
  • Duration: 90 minutes
  • Output: Interview plan with methodology, questions, biases to avoid

2. Recruit Participants

  • Target: 5-10 customers per discovery cycle (Teresa Torres: continuous discovery = 1 interview/week)
  • Segment: Focus on personas from Phase 1
  • Recruitment channels:
    • Existing customers (email, in-app prompts)
    • Churned customers (exit interviews)
    • Cold outreach (LinkedIn, communities)
  • Incentive: $50-100 gift card or product credit
  • Duration: 2-3 days (parallel with Phase 1)

3. Schedule Interviews

  • Format: 45-60 min per interview (30-40 min conversation + buffer)
  • Timeline: Spread across 1-2 weeks
  • Recording: Get consent, record for synthesis

Outputs from Phase 2

  • Interview guide: 5-7 open-ended questions (Mom Test style)
  • Participant roster: 5-10 scheduled interviews
  • Synthesis plan: How you'll capture and analyze insights

Phase 3: Conduct Research (Week 1-2)

Goal: Gather qualitative evidence through customer interviews.

Activities

1. Conduct Discovery Interviews

  • Methodology: From skills/discovery-interview-prep/SKILL.md (Problem validation, JTBD, switch interviews, etc.)
  • Participants: PM + optional observer (design, eng)
  • Duration: 5-10 interviews over 1-2 weeks
  • Focus areas:
    • Past behavior (not hypotheticals): "Tell me about the last time you [experienced this problem]"
    • Workarounds: "How do you currently handle this?"
    • Alternatives tried: "Have you tried other solutions? Why did you stop?"
    • Pain intensity: "How much time/money does this cost you?"

2. Take Structured Notes

  • Template:
    • Participant: [Name, role, company size]
    • Context: [When/where they experience problem]
    • Actions: [What they do, step-by-step]
    • Pain points: [Frustrations, blockers]
    • Workarounds: [Current solutions]
    • Quotes: [Verbatim customer language]
    • Insights: [Patterns, surprises]

3. Review Support Tickets & Analytics (Parallel)

  • Support tickets: Tag by theme (onboarding, feature confusion, bugs)
  • Analytics: Identify drop-off points, feature usage, cohort behavior
  • Surveys: Review NPS comments, exit surveys, feature requests

Outputs from Phase 3

  • Interview transcripts: Recorded sessions + detailed notes
  • Support ticket themes: Top 10 issues by frequency
  • Analytics insights: Quantitative data on behavior (e.g., "60% abandon onboarding at step 3")

Decision Point 2: Have we reached saturation?

Saturation = same pain points emerge across 3+ interviews, no new insights

If YES (saturated after 5-7 interviews): Proceed to Phase 4 (Synthesis)

If NO (still learning new things): Schedule 3-5 more interviews

  • Time impact: +1 week

Phase 4: Synthesize Insights (End of Week 2)

Goal: Identify patterns, prioritize pain points, map opportunities.

Activities

1. Affinity Mapping (Thematic Analysis)

  • Method:
    • Write each insight/quote on sticky note
    • Group by theme (e.g., "onboarding confusion," "pricing objections," "mobile access")
    • Count frequency (how many customers mentioned each theme)
  • Participants: PM, design, optional eng
  • Duration: 90-120 minutes
  • Output: Themed clusters with frequency counts

2. Create Customer Journey Map (Optional)

  • Use: skills/customer-journey-mapping-workshop/SKILL.md (interactive)
  • When: If pain points span multiple phases (discover, try, buy, use, support)
  • Duration: 90 minutes
  • Output: Journey map with opportunities ranked by impact

3. Prioritize Pain Points

  • Criteria:
    • Frequency: How many customers mentioned this?
    • Intensity: How painful is it? (time wasted, money lost, emotional frustration)
    • Strategic fit: Does solving this align with business goals?
  • Method: Score each pain point (1-5) on frequency, intensity, strategic fit
  • Output: Ranked list of top 3-5 pain points to address

4. Update Problem Statement

  • Use: skills/problem-statement/SKILL.md (component)
  • Refine based on research: Did initial hypothesis hold? Adjust if needed.
  • Output: Validated problem statement

Outputs from Phase 4

  • Affinity map: Themes with frequency counts
  • Top 3-5 pain points: Prioritized by frequency × intensity × strategic fit
  • Customer quotes: 3-5 verbatim quotes per pain point
  • Validated problem statement: Refined based on evidence

Phase 5: Generate & Validate Solutions (Week 3)

Goal: Explore solution options, design experiments, validate assumptions.

Activities

1. Generate Opportunity Solution Tree

  • Use: skills/opportunity-solution-tree/SKILL.md (interactive)
  • Input: Top 3 pain points from Phase 4
  • Participants: PM, design, engineering lead
  • Duration: 90 minutes
  • Output: 3 opportunities, 3 solutions per opportunity, POC

Truncated for display — read the full file on GitHub.

Related Skills

View on GitHub
GitHub Stars7.1k
CategoryProduct
Updated2mo ago
Forks846

Languages

Shell

Trust signals

88/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

1 medium
discovery-process — Universal Skill: Install & Safety Check | SkillAgent