Help us improve
Share bugs, ideas, or general feedback.
From ai-toolkit
Generates a Mom Test customer interview script for a product or feature. Includes opening rapport-builder, workflow questions, pain probes, and red flag warnings.
npx claudepluginhub c0x12c/ai-toolkit --plugin ai-toolkitHow this command is triggered — by the user, by Claude, or both
Slash command
/ai-toolkit:interview [product or feature name]spartan/The summary Claude sees in its command listing — used to decide when to auto-load this command
# Interview Script: {{ args[0] | default: "your product" }}
You are generating a user interview script based on **The Mom Test** by Rob Fitzpatrick.
The core idea: even your mom will lie to you about your startup idea. So don't ask about your idea — ask about their life.
---
## The Mom Test Rules (ALWAYS enforce these)
1. **Talk about their life, not your idea.** Don't pitch. Don't describe what you're building. Ask about what they do today.
2. **Ask about specifics in the past, not generics or the future.** "Tell me about the last time you..." beats "Would you ever..."
3. **Talk less,.../review-questionsReviews interview questions against Mom Test principles, detecting leading, opinion-based, or confirmation-biased questions and proposing alternatives. Outputs a table of issues and fixes.
/interview-customersDesign and conduct structured customer interviews to understand problems deeply.
/interviewPrepares customer interview scripts or summarizes transcripts into structured insights.
/interviewConducts deep discovery interview for engineering, brand, product, marketing, or sales domains, asking targeted questions to reveal unthought aspects and refine specifications conversationally.
/interviewPrepare an interview script or summarize an interview transcript into structured insights.
/validate-ideaPressure-tests a product idea by analyzing the weakest assumption, missing buyer, and competitive alternatives. Redirects from validation theater toward genuine customer conversations.
Share bugs, ideas, or general feedback.
You are generating a user interview script based on The Mom Test by Rob Fitzpatrick.
The core idea: even your mom will lie to you about your startup idea. So don't ask about your idea — ask about their life.
| Red Flag | What It Really Means | What to Do Instead |
|---|---|---|
| "That sounds great!" | They're being polite | Ask: "When was the last time you had this problem?" |
| "I would definitely use that" | Future promises are worthless | Ask: "What did you do LAST TIME this happened?" |
| "Yeah, that's a problem" | Generic agreement, no signal | Ask: "Can you walk me through the last time?" |
| "I'd pay for that" | Talk is cheap | Ask: "How much do you spend on [current solution] now?" |
| They change the subject | They don't actually care | Note it. This problem isn't top of mind for them. |
Based on {{ args[0] }}, generate a ready-to-use script. Ask the user first:
"In 1-2 sentences, what problem does {{ args[0] }} solve and who has this problem?"
Then generate the full script:
Goal: Build rapport. Set the frame. Don't bias them.
Script:
"Thanks for taking the time. I'm trying to understand how people
deal with [problem area — NOT your solution]. I'm not selling anything.
I just want to learn about your experience.
There are no right or wrong answers. I'm most interested in stories
about what you actually do day to day."
DO NOT say: "I'm building X and want your feedback." That biases everything.
Goal: Understand their current workflow. What do they do today?
For each answer: Follow up with "Can you give me a specific example?" and "When was the last time that happened?"
Goal: How bad is the problem? Are they actively trying to fix it?
Key signal: If they haven't tried to solve it or spent money on it, the pain might not be bad enough.
Goal: Is this a top-3 problem or just a minor annoyance?
Key signal: If it's not in their top 3, they won't pay for a solution or change their behavior.
Goal: Get referrals and next steps.
Script:
"This has been really helpful. A couple more quick things:
- Is there anything about [problem area] that I should have asked
but didn't?
- Do you know 2-3 other people who deal with this same problem?
I'd love to talk to them too.
- Would it be okay if I followed up in a few weeks with a quick update?"
After the interview, score the signal strength:
| Signal | Score | What It Means |
|---|---|---|
| They described the problem with emotion and detail | STRONG | Real pain, they care |
| They've spent money or significant time trying to solve it | STRONG | Willing to pay |
| They asked YOU when it would be ready | STRONG | Pull signal — they want this |
| They offered to introduce you to others with the problem | STRONG | They think this matters |
| They gave generic answers, no specific stories | WEAK | Problem might not be real for them |
| They were polite but didn't share any struggles | WEAK | No pain here |
| They said "cool idea" but had no personal experience | NONE | Wrong person or wrong problem |
Count your signals:
Show the user:
Remind the user: Talk to at least 5 people before making any decisions. One interview is not enough data.
Next step: After 5+ interviews, run /spartan:validate to score the idea based on what you learned.