intended-vs-implemente…
The method for finding the gap between what a system is supposed to do and what the code actually does — the class of bug generic scanners miss because they…
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
$ npx -y skills add phuryn/pm-skills --skill interview-script --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/interview-scriptContext preview
The summary Claude sees to decide when to auto-load this skill.
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
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."
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.
1. **Clarify research objectives**:
2. **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:
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.
---
68 PM skills and 42 chained workflows across 9 plugins. Claude Code, Cowork, and more. From discovery to strategy, execution, launch, growth, and shipping AI-built code. Designed for Claude Code and Cowork. Skills compatible with other AI assistants.
Repo: phuryn/pm-skills
The method for finding the gap between what a system is supposed to do and what the code actually does — the class of bug generic scanners miss because they…
The durable documentation set that makes an AI-built (vibe-coded) app reviewable before shipping. A small core every app needs — architecture, user/permission…
Analyze A/B test results with statistical significance, sample size validation, confidence intervals, and ship/extend/stop recommendations. Use when evaluating…
Perform cohort analysis on user engagement data — retention curves, feature adoption trends, and segment-level insights. Use when analyzing user retention by…
Generate SQL queries from natural language descriptions. Supports BigQuery, PostgreSQL, MySQL, and other dialects. Reads database schemas from uploaded…
Brainstorm team-level OKRs aligned with company objectives — qualitative objectives with measurable key results. Use when setting quarterly OKRs, aligning team…