Discovery Interview Prep

This walks you through prepping customer discovery interviews by asking about your research goal (problem validation, churn investigation, etc.), target segment, and constraints, then recommends a methodology and generates an interview framework. It's built on the workshop-facilitation protocol, so expect 3-4 adaptive questions with numbered options at each step. What I like here is the bias-aware approach: it explicitly calls out anti-patterns like leading questions and confirmation bias, which is where most discovery interviews fall apart. Best for product managers who need to design an interview plan from scratch rather than just grab a generic script. Won't help with usability testing or quantitative research, those need different frameworks entirely.

skills.sh installs: 3.1K
GitHub stars: 7.9K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add deanpeters/product-manager-skills --skill discovery-interview-prep --agent claude-code

Installs into .claude/skills of the current project.

Files

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.

SKILL.md on GitHub