PluginBench
Skill
Pass
Audit score 90

interview-script

phuryn/pm-skills

Generate structured customer interview scripts with JTBD questions following The Mom Test principles.

What is interview-script?

Creates a complete interview script for user research that surfaces real insights through past behavior, not opinions. Includes warm-up, core exploration with Jobs-to-Be-Done probing, and wrap-up sections, plus a note-taking template. Use when preparing discovery interviews, validating assumptions, or planning research that informs product decisions.

  • Generates opening, warm-up, core exploration, and wrap-up sections tailored to your research objectives
  • Includes Jobs-to-Be-Done probing questions focused on past behavior and specific instances
  • Applies The Mom Test principles: no leading questions, no pitching, 80/20 listening-to-talking ratio
  • Provides probing techniques (Tell me more, Why, Specific examples, What happened next, How did that feel)
  • Creates a note-taking template to capture key findings during interviews
  • Helps clarify research objectives and assumptions before writing the script

How to install interview-script

npx skills add https://github.com/phuryn/pm-skills --skill interview-script
Claude Code
Cursor
Windsurf
Cline

How to use interview-script

  1. 1.Provide the research topic or product area you want to explore (via $ARGUMENTS)
  2. 2.Optionally share supporting files like personas, hypotheses, product briefs, or previous interview notes
  3. 3.Review the generated script sections: opening, warm-up, core exploration, wrap-up
  4. 4.Customize questions to match your specific product area, persona, and research objectives
  5. 5.Use the included note-taking template during interviews to capture key findings
  6. 6.Conduct interviews following The Mom Test principles: ask about their life and past behavior, not your idea

Use cases

Good for
  • Preparing for user discovery interviews to validate product hypotheses
  • Creating interview guides for the Product Trio (PM, Designer, Engineer) to use together
  • Planning research to inform Stage 1 (Explore) discovery activities
  • Developing scripts for customer interviews on a specific product area or user pain point
  • Documenting interview structure and findings for cross-functional teams
Who it's for
  • Product managers conducting continuous discovery research
  • Product designers collaborating on user research
  • Teams preparing for customer validation interviews
  • Anyone planning structured user interviews or discovery sessions

interview-script FAQ

What's the difference between this and a regular survey or questionnaire?

This creates a conversational interview script focused on understanding past behavior and emotions through open-ended probing, not yes/no questions. It follows The Mom Test to avoid leading questions and opinions.

How long should a customer interview be?

The script is designed for 30-45 minutes total: 2-3 min opening, 5 min warm-up, 15-20 min core exploration, 3-5 min wrap-up. Adjust sections based on available time.

Can I use this for internal stakeholder interviews?

Yes. The script structure works for stakeholder interviews too, though you may adjust the context and questions to focus on their perspective and decision-making rather than end-user behavior.

Should the whole Product Trio attend interviews?

The skill supports trio collaboration. Having PM, Designer, and Engineer present provides multiple perspectives, but ensure the interview doesn't become overwhelming for the participant. Consider splitting responsibilities.

What if I don't have a specific hypothesis yet?

Start by clarifying your research objectives: What decisions does this research inform? What assumptions need validation? The script will help you explore broadly, then narrow based on what you learn.

Full instructions (SKILL.md)

Source of truth, from phuryn/pm-skills.


name: interview-script description: "Create a structured customer interview script with JTBD probing questions, warm-up, core exploration, and wrap-up sections. Follows The Mom Test principles — no leading questions, no pitching, focus on past behavior. Use when preparing for user interviews, creating interview guides, or planning discovery research."

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)
    • Set expectations: "There are no right or wrong answers. We're here to learn from your experience."
    • Ask permission to record (if applicable)
    • Confirm time available

    Warm-Up: Context & Background (5 min)

    • "Tell me about your role and what a typical day/week looks like."
    • "How long have you been doing [activity related to the product area]?"
    • Goal: Build rapport and understand their context

    Core Exploration: Jobs to Be Done (15-20 min)

    Current situation and behavior (past tense, specific instances):

    • "Walk me through the last time you [did the thing we're exploring]. What happened?"
    • "What tools or methods did you use?"
    • "How long did it take? Who else was involved?"

    Pain points and frustrations (observe, don't lead):

    • "What was the hardest part about that?"
    • "If you could wave a magic wand, what would change?"
    • "What have you tried to solve this? What happened?"

    Desired outcomes (their words, not yours):

    • "What does 'good' look like for you in this area?"
    • "How would you know if this was working well?"

    Willingness to pay / priority (skin in the game):

    • "How much time/money do you currently spend on this?"
    • "Have you looked for a better solution? What did you find?"
    • "What would you give up to have this solved?"

    Probing Techniques

    Use these when you hit an interesting thread:

    • "Tell me more about that" — opens up any topic
    • "Why?" (asked gently, 2-3 times) — gets to root causes
    • "Can you give me a specific example?" — moves from opinions to facts
    • "What happened next?" — follows the story
    • "How did that make you feel?" — captures emotional intensity

    The Mom Test Rules

    • Ask about their life, not your idea
    • Ask about the past, not the future ("Would you use X?" is useless)
    • Talk less, listen more — aim for 80/20 split
    • Never pitch during the interview
    • Look for strong emotions — they signal real pain or delight
    • Compliments are noise — "That sounds cool!" tells you nothing

    Wrap-Up (3-5 min)

    • "Is there anything I didn't ask that you think is important?"
    • "Who else should I talk to about this?"
    • Thank them for their time
    • Share next steps (if any)
  3. Customize the script: Adapt questions to the specific product area, persona, and research objectives. Add or remove sections based on the interview length available.

  4. Include a note-taking template:

    Participant: [Name / ID]
    Date: [Date]
    Key Jobs: [What they're trying to accomplish]
    Current Solution: [What they use today]
    Biggest Pain: [Their #1 frustration]
    Desired Outcome: [What success looks like]
    Willingness to Pay: [How much they invest / would invest]
    Surprise Finding: [Something unexpected]
    Follow-up: [Next steps]
    

Save as markdown. Include both the script and the note-taking template.


Further Reading