dotfiles/dot_config/skillshare/skills/interview-script/SKILL.md
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.
npx skillsauth add pkking/dotfiles interview-scriptInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
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.
testing
Reference for writing and editing skills well — the vocabulary and principles that make a skill predictable.
tools
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
tools
Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui). Use for complex artifacts requiring state management, routing, or shadcn/ui components - not for simple single-file HTML/JSX artifacts.
data-ai
Plan a huge chunk of work — more than one agent session can hold — as a shared map of investigation tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.