Skip to main content
command CX Codex

interview · phuryn — Claude Code command: what it does, how to install

Builds customer interview scripts using The Mom Test principles or converts raw interview transcripts into structured Jobs to Be Done insights.

MIT ★ 28,211 updated 2026-10-16

Install into Claude Code · Plugin marketplace All methods and platforms ↓
/plugin marketplace add phuryn/pm-skills
/plugin install pm-product-discovery@pm-skills
Open on GitHub

What interview does

The command operates in two modes: before you talk to customers and after the call. In prep mode, the assistant clarifies your research goal, audience segment, and interview length. It then generates a timed discussion guide complete with a note-taking template and red flags to watch for when participants give polite, unhelpful feedback. Questions target past actions rather than theoretical promises.

For post-interview analysis, summarize mode processes pasted transcripts, text files, or rough call notes. It extracts Jobs to Be Done, pain point severity tables, verbatim quotes, and invalidated assumptions. If a participant contradicts themselves by describing one preference but practicing another, the summary highlights that discrepancy directly.

The output saves as Markdown. Without an argument, the command asks interactively whether to prepare a script or process notes.

What it helps with

  • draft customer interview guides grounded in The Mom Test
  • convert raw interview transcripts into Jobs to Be Done frameworks
  • detect contradictions between stated user opinions and actual habits
  • compile structured tables of customer pain points and direct quotes

Example prompts for the agent

  • /interview prep Onboarding experience for enterprise users
  • /interview summarize [paste transcript or upload file]
  • /interview

How to install interview

1Plugin marketplace

/plugin marketplace add phuryn/pm-skills
/plugin install pm-product-discovery@pm-skills

2Manually: put the files in place

.claude/commands/interview.md

Call it with /interview. For all projects use ~/.claude/commands/

Questions about interview

How do I install the interview command in Claude Code?

Run /plugin marketplace add phuryn/pm-skills in your terminal, then install it with /plugin install pm-product-discovery@pm-skills.

What input formats does summarize mode accept?

It accepts pasted transcripts, uploaded text files, or meeting notes. If only a brief summary is available, the command works with those notes and notes any limitations.

How does prep mode structure interview scripts?

It organizes questions into warm-up, core exploration, and wrap-up sections based on your available time. Each question includes an explanation of why you are asking it and follow-up prompts.

Source text

interview.md · MIT
---
description: Prepare a customer interview script or summarize an interview transcript into structured insights
argument-hint: "[prep|summarize] <topic or transcript>"
---

# /interview -- Customer Interview Prep & Summary

Two modes: **prep** creates a structured interview script before you talk to customers, **summarize** extracts insights after you've done the interview.

## Invocation

```
/interview prep Onboarding experience for enterprise users
/interview summarize [paste transcript or upload file]
/interview                    # asks which mode you need
```

## Modes

---

### Prep Mode

Create a structured interview script tailored to your research question.

#### Workflow

**Step 1: Understand the Research Goal**

Ask the user:
- What are you trying to learn? (specific research question)
- Who are you interviewing? (segment, role, relationship to product)
- How much time do you have? (15 min, 30 min, 60 min)
- What decisions will this research inform?

**Step 2: Generate Interview Script**

Apply the **interview-script** skill:

- Follow "The Mom Test" principles — ask about their life, not your idea
- No leading questions, no pitching, focus on past behavior and real situations
- Structure the script in sections:

```
## Interview Script: [Research Topic]

**Research Question**: [what we're trying to learn]
**Target Participant**: [who]
**Duration**: [X] minutes

### Warm-up (3-5 min)
[Rapport-building questions, role/context understanding]

### Core Exploration (15-40 min)
[JTBD probing, past behavior, current workflow, pain points]
- For each question: the question + why you're asking it + follow-up prompts

### Specific Topics (5-10 min)
[Targeted questions about specific features or concepts — if needed]

### Wrap-up (3-5 min)
[Open-ended closing, referral ask, next steps]

### Note-Taking Template
[Pre-formatted template to capture insights during the interview]

### Red Flags to Watch For
[Signs the conversation is going off-track or the participant is being polite rather than honest]
```

**Step 3: Customize and Review**

- Adjust question count to fit the time slot
- Add probing questions for specific hypotheses the user wants to test
- Flag questions that might lead the witness
- Offer a printable version (markdown file saved to workspace)

---

### Summarize Mode

Transform an interview transcript into structured, actionable insights.

#### Workflow

**Step 1: Accept the Transcript**

Accept in any format:
- **Pasted text**: Raw transcript or notes
- **Uploaded file**: Document, text file, or meeting notes export
- **Audio summary**: If the user describes what was said (not a full transcript)

If the input is rough notes rather than a full transcript, work with what's available and note the limitations.

**Step 2: Extract and Structure**

Apply the **summarize-interview** skill:

Parse the transcript to identify:
- **Participant profile**: Role, experience level, segment, context
- **Jobs to Be Done**: What the participant is trying to accomplish
- **Current workflow**: How they solve the problem today
- **Pain points**: Frustrations, workarounds, time sinks
- **Satisfaction signals**: What works well, moments of delight
- **Quotes**: Verbatim quotes that capture key insights (with timestamps if available)
- **Surprises**: Anything unexpected or that contradicts assumptions
- **Feature reactions**: If specific features/concepts were discussed, capture reactions

**Step 3: Generate Interview Summary**

```
## Interview Summary

**Participant**: [anonymized profile — role, segment, experience]
**Date**: [if known]
**Duration**: [if known]
**Interviewer**: [if known]

### Key Insights
1. **[Insight]** — [supporting evidence/quote]
2. **[Insight]** — [supporting evidence/quote]
3. ...

### Jobs to Be Done
- **Primary JTBD**: [When I..., I want to..., so I can...]
- **Related JTBDs**: [additional jobs]

### Current Workflow
[How the participant currently solves the problem, step by step]

### Pain Points
| Pain Point | Severity | Quote |
|-----------|----------|-------|

### Satisfaction Signals
| What Works | Why | Quote |
|-----------|-----|-------|

### Notable Quotes
> "[quote]" — on [topic]

### Assumptions Validated / Invalidated
| Assumption | Status | Evidence |
|-----------|--------|----------|

### Action Items
- [ ] [Follow-up action from this interview]
- [ ] [Research question to explore further]

### Raw Notes
[If helpful, include annotated key sections]
```

Save the summary as a markdown file.

**Step 4: Connect to Broader Research**

Offer:
- "Want me to **compare this with other interview summaries** you've done?"
- "Should I **update assumptions** based on what this participant said?"
- "Want me to **extract personas** from multiple interviews?"

## Notes

- In prep mode, always include "why you're asking" annotations — they help the interviewer stay on track
- In summarize mode, distinguish between what the participant *said* vs. what they *did* (behavioral > stated)
- Flag contradictions within the same interview (says one thing, describes doing another)
- If the transcript mentions competitor products, capture competitive intelligence
- For summarize mode, if multiple transcripts are provided, synthesize across them with cross-participant patterns

© Paweł Huryn · MIT · phuryn/pm-skills

Similar slash commands

All slash commands for Notes, tasks and projects →

interview by other authors comes first.

interview jarrodwatts interview runs a long question-and-answer session about a plan file and writes the finished spec back to the same path. CX Codex +1 ★ 1,064repo stars interview-mapper Alireza Rezvani interview-mapper codes interview transcripts into structured mappings across 16 lenses, verifies every claim against verbatim quotes, and highlights disagreements between repeated runs. CX Codex +1 3installs mom-test wondelai Refines customer interview scripts using Mom Test principles, replacing leading questions with past-behavior facts. Useful when validating ideas without false positives. CX Codex +1 6,100installs asb-interview-goals asmartbear asb-interview-goals helps draft and refine numbered goal questions for customer discovery before saving them into GOALS.md. Useful when planning customer interviews or validating a business idea. CX Codex +1 730installs discovery-interview-prep deanpeters discovery-interview-prep guides product teams through planning customer discovery conversations. It sets up target segments, frames research goals, and filters out bias before you speak with users. CX Codex +1 3,200installs discover-interview-synthesis product-on-purpose The discover-interview-synthesis skill turns interview notes and transcripts into themes, quotes, insights and recommendations. Useful after a round of user research when the team needs to see what you heard. CX Codex +1 866installs user-needs-map haabe Maps user needs with Rich Allen's User Needs Mapping method. It separates needs from solutions and flags underserved ones for an Opportunity Solution Tree. CX Codex +1 ★ 54repo stars

From the same set120

The whole set →
market-scan market-scan — a command for strategic analysis of competitive landscape. Runs SWOT, PESTLE, Porter's Five Forces, and Ansoff Matrix together and delivers a unified report with cross-framework synthesis. CX Codex +1 ★ 28,211repo stars discover Runs a structured product discovery cycle from initial ideation to experiment design. Useful for testing product hypotheses before writing code. CX Codex +1 ★ 28,211repo stars brainstorm brainstorm — a Claude Code command that produces product ideas or validation experiments from PM, designer and engineer viewpoints, for either an existing product or a new concept. CX Codex +1 ★ 28,211repo stars sprint Three modes for sprint lifecycle: plan sprints with capacity estimates and task selection, run retrospectives with structured feedback, generate release notes from technical artifacts. CX Codex +1 ★ 28,211repo stars business-model Builds a business model with Lean Canvas, Business Model Canvas, Startup Canvas, or Value Proposition. Useful for testing ideas and shaping product strategy. CX Codex +1 ★ 28,211repo stars pm-ai-shipping The pm-ai-shipping plugin relocated to phuryn/product-engineering as the ai-shipping plugin, now with a release gate and independent review. Pointers here show where each skill and command went. ★ 28,211repo stars pm-toolkit pm-toolkit is a Claude Code plugin for product managers to draft NDAs and privacy policies, proofread product copy, and review resumes. ★ 28,211repo stars pm-marketing-growth pm-marketing-growth — a Claude Code plugin for marketing ideas, value propositions, North Star Metrics, product naming, and positioning work. ★ 28,211repo stars

Project sponsors

Companies that keep this analytics open