interview-script▌
phuryn/pm-skills · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
Create a structured interview script that surfaces real insights, not just opinions. Follows "The Mom Test" principles — ask about their life, not your idea.
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
-
Clarify research objectives:
- What specific questions does the team need answered?
- What decisions will this research inform?
- What assumptions need validation?
-
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)
-
Customize the script: Adapt questions to the specific product area, persona, and research objectives. Add or remove sections based on the interview length available.
-
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
How to use interview-script on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add interview-script
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches interview-script from GitHub repository phuryn/pm-skills and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate interview-script. Access the skill through slash commands (e.g., /interview-script) or your agent's skill management interface.
Security & Verification Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases▌
User Story & Requirements Generation
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Competitive Analysis
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Roadmap Prioritization
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
Make data-driven prioritization decisions faster
Stakeholder Communication
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client
- ›Access to product documentation and roadmap tools (Jira, Notion, etc.)
- ›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
- ›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Installation Steps
- 1.Install product management skill
- 2.Start with user story generation for known feature
- 3.Progress to competitive analysis: research 2-3 competitors
- 4.Use for roadmap prioritization: apply RICE/ICE scoring
- 5.Draft stakeholder communications and refine based on feedback
- 6.Build template library for recurring PM tasks
- 7.Share effective prompts with product team
Common Pitfalls
- ⚠Not validating competitive research—verify facts before sharing
- ⚠Accepting user stories without involving engineering team
- ⚠Over-relying on frameworks without qualitative judgment
- ⚠Not customizing outputs to company culture and communication style
- ⚠Skipping stakeholder validation of generated requirements
Best Practices▌
✓ Do
- +Validate research and competitive analysis with real data
- +Collaborate with engineering when generating technical requirements
- +Customize frameworks and templates to your company context
- +Use skill for first drafts, refine with stakeholder input
- +Document successful prompt patterns for PM tasks
- +Combine AI efficiency with human judgment and intuition
✗ Don't
- −Don't publish competitive analysis without fact-checking
- −Don't finalize user stories without engineering review
- −Don't make prioritization decisions solely on AI scoring
- −Don't skip customer validation of generated requirements
- −Don't ignore company-specific context and culture
💡 Pro Tips
- ★Provide context: company goals, constraints, customer feedback
- ★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
- ★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
- ★Use skill for 70% generation + 30% customization to company needs
When to Use This▌
✓ Use When
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid When
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
Learning Path▌
- 1Basic: user stories, feature specs, status updates
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.8★★★★★28 reviews- ★★★★★Neel Lopez· Dec 20, 2024
Keeps context tight: interview-script is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Dhruvi Jain· Dec 16, 2024
We added interview-script from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Neel Kapoor· Dec 12, 2024
We added interview-script from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Zara Lopez· Nov 11, 2024
interview-script is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Oshnikdeep· Nov 7, 2024
Useful defaults in interview-script — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Liam Rao· Nov 3, 2024
Useful defaults in interview-script — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Ganesh Mohane· Oct 26, 2024
Registry listing for interview-script matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Jin Thomas· Oct 22, 2024
Registry listing for interview-script matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Soo Thomas· Oct 2, 2024
Solid pick for teams standardizing on skills: interview-script is focused, and the summary matches what you get after install.
- ★★★★★Zara Sharma· Sep 21, 2024
interview-script has been reliable in day-to-day use. Documentation quality is above average for community skills.
showing 1-10 of 28