Mastering `mom-test`: The Complete Guide

In the era of Vibe Coding, speed is no longer the bottleneck. With tools like Gemini CLI and autonomous agents, you can move from a vague “vibe” to a deployed, functional prototype in a single afternoon. But this newfound velocity comes with a hidden, lethal danger: the ability to build the wrong thing faster than ever before.

The greatest risk to a Vibe Coder isn’t a syntax error or a hallucinating LLM; it’s Hallucinated Demand. You have an idea, it feels brilliant, you ask a few friends or Twitter followers if they “would use it,” they say “yes” because they want to be supportive, and you spend your weekend orchestrating a complex multi-agent workflow to build it. On Monday, you launch to a chorus of silence.

This is where the mom-test skill becomes the most critical asset in your technical stack. Derived from Rob Fitzpatrick’s seminal work, the Mom Test is a set of rules for talking to customers and getting real, unbiased feedback—even when the person you’re talking to (like your mom) wants to lie to you to protect your feelings.

In Vibe Coding, we use the mom-test to ensure our “vibe” is grounded in a real-world problem. This guide will show you how to master the art of discovery so that every line of code your agents write is solving a validated pain point.

The Core Problem: The Compliment Trap

Why do most customer interviews fail? Because human beings are conditioned to be nice. If you ask, “Do you think this AI-powered task manager is a good idea?” you are practically begging for a compliment.

Compliments are the “death rattle” of a startup idea. They feel good, but they provide zero data. In Vibe Coding, a compliment is dangerous because it provides the psychological “fuel” to trigger a high-resource cm-execution phase on a product that no one actually wants to pay for.

The mom-test solves this by forcing you to stop talking about your idea and start talking about the customer’s life.

The Three Rules of the Mom Test

To master this skill, you must internalize three fundamental shifts in how you approach research.

1. Talk About Their Life, Not Your Idea

Your idea is a distraction. The moment you mention your “AI-powered solution,” the interview is over. The customer shifts into “critic mode” or “supportive friend mode.” Instead, ask about the problems they are already facing.

Bad Vibe: “I’m building a tool that uses agents to automate your email. Would that help you?”
Mom Test Vibe: “Tell me about the last time you felt overwhelmed by your inbox. What did you do to fix it?“

2. Ask About Specifics in the Past, Not Opinions About the Future

Humans are notoriously bad at predicting their future behavior. We all think we’ll go to the gym next week, and we all think we’ll use that new productivity app. Future-tense questions (“Would you…”, “How often might you…”) generate Bad Data. Past-tense questions (“When was the last time…”, “How do you currently…”) generate Hard Evidence.

3. Talk Less, Listen More

The goal of a discovery session is to be surprised. If you are doing the talking, you are pitching. If you are pitching, you aren’t learning. Your goal is to identify a “hair-on-fire” problem that is so painful the user has already tried (and failed) to solve it with existing tools.

Integrating `mom-test` into the Vibe Coding Workflow

In a traditional development cycle, user research happens in the “Requirements” phase. In Vibe Coding, the mom-test should be a “Pre-Flight” check before you even touch a PLANNING.md or a product.md.

The “Critical Mom” Agent Prompt

You can use AI to simulate the mom-test before you go out into the real world. By prompting an agent to be a “Critical Mom,” you can stress-test your own assumptions.

Example Prompt:

“I am going to describe a product idea. I want you to act as a ‘Critical Mom’ who is currently experiencing [Pain Point]. Do not give me any compliments. Do not tell me the idea is good. Instead, ask me 5 questions about my past behavior regarding this problem that would prove I am actually willing to pay for a solution. Use the Mom Test framework: no future-tense questions, only past-tense specifics.”

Validating the “Vibe”

Before you use the cm-planning skill, you should have at least three “Validated Learning” points from mom-test interviews. These are not “people said they liked it” points; they are “people showed me how they are currently wasting $200/month on a manual workaround” points.

Interactive Example: From Vibe to Reality

Let’s look at a real-world scenario. You want to build a “Smart Meeting Summarizer” for Vibe Coders.

The Failed Interview (The Nice Mom)

You: “Hey, I have this vibe for an AI agent that joins your Zoom calls, listens to the technical jargon, and automatically updates your task_plan.md. Do you think that’s cool?” User: “Oh wow, yeah! I hate taking notes. That sounds super helpful. I’d definitely use that.” Result: You spend 10 hours building it. The user never installs it because “it’s not a priority right now.”

The Successful Mom Test (The Hard Truth)

You: “How do you handle documenting your technical decisions after a pair-programming session?” User: “Honestly, I usually forget. I just hope I remember the ‘vibe’ when I start coding.” You: “When was the last time that caused a major bug or a rewrite?” User: “Last Tuesday. I spent 4 hours building a feature we decided to cut because I didn’t write down the meeting notes.” You: “What have you tried to do to stop that from happening?” User: “I tried recording the calls, but I never watch them back. Too much effort.” You: “Why not just use a standard AI transcriber?” User: “They don’t understand the Gemini CLI syntax I use. I have to spend 20 minutes fixing the transcript anyway, so I just stopped using them.”

The Insight: The problem isn’t “notetaking.” The problem is Context-Aware Documentation for Specialized CLI Workflows. Now, your cm-planning phase has a surgical target.

Best Practices & Tips for Vibe Coders

1. The “Why” is a Trap

Don’t ask “Why do you need this?” Ask “What happened that made you look for a solution?” The “What” leads to a story; the “Why” leads to a rationalization. Stories contain the truth; rationalizations contain what people think you want to hear.

2. Identify “Commitment” and “Advancement”

A successful discovery session ends with a commitment. This could be:

Time: “Can we meet again on Thursday so I can show you how I’d solve that specific CLI documentation issue?”
Reputation: “Who else in your team is feeling this pain? Can you introduce me?”
Cash: (The ultimate validator) “I’m running a small beta for $50 to solve this. Are you in?”

If they aren’t willing to give you a clear “Advancement,” they don’t actually have the problem.

3. Use `cm-jtbd` (Jobs To Be Done) as a Follow-up

Once you have the mom-test data, use the cm-jtbd skill to map the “Job” the user is hiring your code to do.

Mom Test: Finds the pain.
JTBD: Maps the desired progress.
Vibe Coding: Implements the solution at lightspeed.

Common Mistakes to Avoid

Pitching in disguise: “Don’t you hate it when [Problem]? Well, I’m building [Solution]…” This is still a pitch. Stay in the problem space.
Collecting “Feature Requests”: Users are great at identifying problems, but they are terrible at designing solutions. If a user says “I need a button that does X,” your response should be “What would happen if you didn’t have that button? What’s the impact?”
The “Ego” Blind Spot: As Vibe Coders, we love our tools. We want to use agents for everything. But sometimes, the mom-test reveals that the user just needs a better README.md, not a complex autonomous agent. Be brave enough to build less.

Conclusion: The Vibe Coding Filter

The mom-test is the ultimate filter for your creative energy. Vibe Coding gives you the power of a 10-person dev team, but the mom-test gives you the wisdom of a seasoned product founder.

Before you trigger your next cm-start or loki-mode session, ask yourself: “Have I spoken to a human about their past struggles, or am I just coding to my own hallucinations?”

Mastering this skill ensures that your speed is directed toward impact. Build for reality, not for compliments. That is the secret to moving from a “vibe” to a sustainable, successful product.

Next Step: Take your current product idea. Find one potential user. Ask them about the last time they faced the problem you’re trying to solve. Do not mention your app. Listen for the “Hard Truth.”

Mastering mom-test: The Complete Guide