Sign in
Explore
Skills · SkillBusiness & OpsResearch & AnalysisProduct managementHR & hiringReviewed

interview-script

Creates a structured customer interview script with jobs-to-be-done probes, following The Mom Test: no leading questions, no pitching, past behavior.

Kind
Skill
Works with
Claude Code, Cursor
Source
PM Skills (Pawel Huryn) @ 2a12295a7717
Path
pm-product-discovery/skills/interview-script/SKILL.md
Jobs
Requirements interviews
Topics
Product management, HR & hiring

Credit

Made by
phuryn
Original
github.com/phuryn/pm-skills/blob/2a12295a7717569baa7be181b4cf…
License
MIT

Listed by Skill Manifest; not made by us.

InstallInstall it from a plugin marketplace.
claude plugin install pm-product-discovery@pm-skills
Install factsScanned 2 Nov 2026
Adds
  • .claude/skills/interview-script/ (the skill folder)
Runs scripts
None found
Uses the network
None found
Needs secrets
None found
Source revision
2a12295a7717
Licence
MIT
Last activity
29 Oct 2026
Review
Reviewed

Found by a static scan of the stored text; nothing is run. “None found” is not a guarantee, so read what you install before you run it.

  • Only the main file is read; other files in the folder are not scanned
## Customer Interview Script

Create a structured interview script that surfaces real insights, not just opinions. Follows "The Mom Test" principles — ask about their life, not your idea.

### Domain Context

Customer interviews are one source in **Stage 1 (Explore)** of continuous discovery. Other sources: stakeholder interviews, usage analytics, data analytics, surveys, market trends, SEO/SEM analysis. The PM needs direct access to users, stakeholders, engineers, and designers — "without proxies." The **Product Trio** (PM + Designer + Engineer — Teresa Torres) should work together on discovery, not just the PM alone.

### Context

You are preparing a customer interview script for research on **$ARGUMENTS**.

If the user provides files (personas, hypothesis lists, product briefs, or previous interview notes), read them first.

### Instructions

1. **Clarify research objectives**:
   - What specific questions does the team need answered?
   - What decisions will this research inform?
   - What assumptions need validation?

2. **Create the interview script** with these sections:

   ### Opening (2-3 min)
   - Introduce yourself and the purpose (learning, not selling)
…