interview-script
by phuryninterview-script helps you create structured customer interview guides with warm-up, core exploration, and wrap-up sections. It follows The Mom Test and JTBD-style probing to keep questions neutral, avoid pitching, and focus on past behavior for discovery, product, and UX research interviews.
This skill scores 78/100, which means it is a solid listing candidate for directory users. It gives a usable, task-specific interview-script workflow with clear trigger language, but users should still expect some manual judgment because the repo lacks supporting assets and deeper operational scaffolding.
- Strong triggerability: the description explicitly says when to use it for user interviews, interview guides, and discovery research.
- Clear workflow intent: the body outlines structured sections like opening, core exploration, and wrap-up, with The Mom Test principles to reduce leading questions.
- Good agent leverage: it includes research-objective clarification and notes to inspect provided files first, which helps an agent adapt the script to context.
- Light supporting infrastructure: there are no scripts, references, resources, or install command, so adoption depends mostly on the SKILL.md content.
- Somewhat limited operational depth: the repo signals a test-like context and the file tree is minimal, so users should verify fit before relying on it for complex research programs.
Overview of interview-script skill
interview-script is a prompt skill for creating structured customer interview guides that help you collect real evidence instead of polished opinions. It is a strong fit for UX researchers, product managers, founders, and designers who need an interview-script skill for discovery work, especially when they want a practical interview-script for UX Research flow built around The Mom Test and JTBD-style probing.
What it does best
This skill turns a rough research goal into a usable script with warm-up, core questions, and wrap-up prompts. It is designed to help you ask about past behavior, current workflows, pain points, and decision context, rather than pitching a concept too early.
When it is the right fit
Use interview-script when you already know the audience and need a high-quality interview guide for a specific research objective. It is most useful for exploratory interviews, problem validation, workflow mapping, and early-stage product discovery.
What makes it different
The main advantage is structure with restraint: it pushes for neutral questions, avoids leading language, and keeps the conversation anchored in actual experience. That makes it more reliable than a generic prompt that only asks for “interview questions.”
How to Use interview-script skill
Install and locate the skill
Run the interview-script install command from the repo’s skill manager context, or add it from phuryn/pm-skills using the project’s install flow. After installation, open pm-product-discovery/skills/interview-script/SKILL.md first; there are no supporting scripts/, references/, or resources/ folders, so the main source of truth is the skill file itself.
Give it the right input
The skill works best when you provide a clear research brief, not a vague topic. Include the target user type, the problem area, the decision the interview should inform, and any known assumptions. A strong prompt looks like: “Create an interview script for UX researchers talking to first-time managers about onboarding pain points; we need to validate where they lose time, what tools they use now, and what triggers a switch.”
Use a workflow, not a one-shot ask
First ask for the script, then review whether the questions map to a real decision. If you already have persona notes, prior interview notes, or a hypothesis list, feed those in before generation. That improves fit more than asking the model to “make it better” after the fact. For interview-script usage, think: brief -> script -> review -> tighten probes -> run interviews.
Read the file in this order
Start with SKILL.md to understand the structure, then look for sections defining context, instructions, and the opening/core/wrap-up pattern. Because the repo is intentionally minimal, the value comes from how precisely you adapt the template to your domain and not from a larger supporting ecosystem.
interview-script skill FAQ
Is interview-script only for UX research?
No. The interview-script skill is useful for any discovery interview where you need honest, behavior-based answers: product discovery, customer development, user research, and stakeholder interviews. It is especially helpful when you need a repeatable script rather than ad hoc questions.
How is it different from a normal prompt?
A normal prompt may generate a list of questions, but interview-script is meant to produce a usable interview flow with purpose, sequencing, and behavioral constraints. That matters because interview quality depends on ordering, neutrality, and follow-up prompts, not just question count.
Is it beginner-friendly?
Yes, if you can describe your audience and research goal. The biggest beginner mistake is asking for “good interview questions” without specifying who you are interviewing or what decision depends on the answers. The skill works best when the input is concrete.
When should I not use it?
Do not use interview-script if you need a broad market survey, a sales call deck, or a fully scripted usability test with task success metrics. It is for discovery conversations, not for every type of research interaction.
How to Improve interview-script skill
Write better inputs than the default brief
The biggest quality jump comes from naming the user, the situation, and the decision you are trying to make. Instead of “make an interview guide for my app,” say what job the user is trying to get done, what you suspect is broken, and what evidence would change your next step.
Ask for probes, not just questions
A strong interview-script guide includes follow-up prompts such as “What happened next?”, “How did you handle that last time?”, and “What did you try before that?” These probes are where the most useful signal usually appears, especially in interview-script for UX Research.
Watch for common failure modes
The most common issues are leading phrasing, too many hypothetical questions, and scripts that skip the participant’s current workflow. If the first output sounds generic, tighten the brief with domain language, known constraints, and the exact behavior you want to uncover. That is the fastest way to improve interview-script usage.
Iterate after the first draft
After you generate the script, edit for neutrality and sequence: warm-up first, then recent examples, then pain, then alternatives, then wrap-up. If you want a stronger second pass, tell the skill what felt too broad, what was missing, and which section needs deeper probing. That turns interview-script install into a practical research workflow, not just a template download.