# Discovery Interview Prep

Plan customer discovery interviews with the right goal, segment, constraints, and method.

- Repository: https://github.com/deanpeters/Product-Manager-Skills (7825 stars)
- Category: Writing
- License: see repository
- Last updated: 2026-10-16
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add deanpeters/Product-Manager-Skills --skill discovery-interview-prep -g -a claude-code -y`
Codex: `npx skills add deanpeters/Product-Manager-Skills --skill discovery-interview-prep -g -a codex -y`
Cursor: `npx skills add deanpeters/Product-Manager-Skills --skill discovery-interview-prep -g -a cursor -y`
Gemini CLI: `npx skills add deanpeters/Product-Manager-Skills --skill discovery-interview-prep -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add deanpeters/Product-Manager-Skills`

## Description

Plan customer discovery interviews with the right goal, segment, constraints, and method. Use when preparing interviews for problem validation, churn research, or new product ideas.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

## Purpose
Guide product managers through preparing for customer discovery interviews by asking adaptive questions about research goals, customer segments, constraints, and methodologies. Use this to design effective interview plans, craft targeted questions, avoid common biases, and maximize learning from limited customer access, ensuring discovery interviews yield actionable insights rather than confirmation bias or surface-level feedback.

This is not a script generator, it's a strategic prep process that outputs a tailored interview plan with methodology, question framework, and success criteria.

## Input

**Works best with:** Your research goal, what you need to learn from customers.
**Also useful:** Customer segment, access constraints (how many interviews, by when), and any hypotheses you're carrying in.

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 skill opens by asking your primary goal for the interviews, then narrows with follow-ups.

**Example invocation:** `Prep interviews to understand why enterprise customers churn after 6 months, I can get 5 interviews in 2 weeks.`

## Key Concepts

### The Discovery Interview Prep Flow
An interactive process that:
1. Gathers product/problem context (marketing materials, assumptions)
2. Defines research goals (what you're trying to learn)
3. Identifies target customer segment and access constraints
4. Recommends interview methodology (Jobs-to-be-Done, problem validation, switch interviews, etc.)
5. Generates interview framework with questions, biases to avoid, and success metrics

The rest: https://github.com/deanpeters/Product-Manager-Skills/blob/HEAD/skills/discovery-interview-prep/SKILL.md