From pm-product-discovery
Generates customer interview scripts with JTBD probing questions and Mom Test principles for user research and discovery planning.
npx claudepluginhub lamngit1995/phuryn-pm-skills --plugin pm-product-discoveryThis skill uses the workspace's default tool permissions.
Browser automation powers web testing, scraping, and AI agent interactions. The difference between a flaky script and a reliable system comes down to understanding selectors, waiting strategies, and anti-detection patterns.
Provides checklists to review code for functionality, quality, security, performance, tests, and maintainability. Use for PRs, audits, team standards, and developer training.
Enforces A/B test setup with gates for hypothesis locking, metrics definition, sample size calculation, assumptions checks, and execution readiness before implementation.
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 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.
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.
Clarify research objectives:
Create the interview script with these sections:
Current situation and behavior (past tense, specific instances):
Pain points and frustrations (observe, don't lead):
Desired outcomes (their words, not yours):
Willingness to pay / priority (skin in the game):
Use these when you hit an interesting thread:
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.