Discovery Interview PrepSAFE

Product Management skills framework built on battle-tested methods for Claude Code, Cowork, Codex, and AI agents.

The instruction file, verbatim from the audited commit — this is the text the model reads, and the surface the audit's instruction layer examines. Quoted here so you can judge it without cloning anything.

---
name: discovery-interview-prep
argument-hint: "[research goal]"
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.
intent: >-
  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.
type: interactive
theme: discovery-research
best_for:
  - "Designing a customer discovery interview plan"
  - "Choosing the right interview methodology for your goals and constraints"
  - "Preparing for research with limited customer access"
scenarios:
  - "I need to interview 5 enterprise customers about why they churned in the last 90 days"
  - "I'm validating a new product idea with a 2-week deadline and cold outreach only"
  - "I want to understand why users aren't activating on our core feature"
estimated_time: "15-20 min"
---


## 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

### Why This Works
- **Goal-driven:** Aligns interview approach to what you need to learn
- **Adaptive:** Adjusts methodology based on product stage (idea vs. existing product) and access constraints
- **Bias-aware:** Highlights common pitfalls (leading questions, confirmation bias, solution-first thinking)
- **Actionable:** Outputs interview guide ready to use

### Anti-Patterns (What This Is NOT)
- **Not a user testing script:** Discovery = learning problems; testing = validating solutions
- **Not a sales demo:** Don't pitch—listen and learn
- **Not surveys at scale:** Deep qualitative interviews (5-10 people), not broad surveys (100+ people)

### When to Use This
- Starting product discovery (validating problem space)
- Repositioning an existing product (understanding new market)
- Investigating churn or drop-off (retention interviews)
- Evaluating feature ideas before building
- Preparing for customer development sprints

### When NOT to Use This
- User testing a prototype (use usability testing frameworks instead)
- Quantitative research at scale (use surveys, analytics)
- When you already know the problem (move to solution validation)

---

### Facilitation Source of Truth

Use [`workshop-facilitation`](../workshop-facilitation/SKILL.md) as the default interaction protocol for this skill.

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 domain-specific assessment content. If there is a conflict, follow this file's domain logic.

## Application

This interactive skill asks **up to 4 adaptive questions**, offering **3-4 enumerated options** at each step.

---

### Step 0: Gather Context (Before Questions)

**Agent suggests:**

Before we design your interview plan, let's gather context:

**For Your Own Product (Existing or Planned):**
- Problem hypothesis or product concept description
- Target customer segment (if known)
- Existing research (support tickets, churn data, user feedback)
- Product website or positioning materials
- Key assumptions you're trying to validate

**For Investigating an Existing Problem:**
- Customer complaints, support tickets, or churn reasons
- Hypotheses about why customers leave or struggle
- Competitive alternatives customers switch to

**If Exploring a New Problem Space:**
- Find similar products or adjacent solutions
- Copy competitor materials, customer reviews (G2, Capterra), or community discussions (Reddit, forums)
- We'll use these to frame hypotheses

**You can paste this content directly, or we can proceed with a brief description.**

---

### Question 1: Research Goal

**Agent asks:**
"What's the primary goal of these di

SAFEgrade B · trust 89/100 Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.

What the source does

Filesystem

none-observed

Network

none-observed

Shell

none-observed

Dependencies

pinned

Secrets in source

none-found

Findings (0)

No findings outside the package's declared scope.

Gates applied: no_behavioural_pass.