agentleFS
deciqAIdeciqAI/knowledge-skills/the-mom-test/SKILL.md

the-mom-test

Skill13 starsChanged 4 months agoMITView on GitHub

Activate when: a founder is about to talk to customers/users to validate an idea; 'I asked people and they loved it', 'how do I run customer interviews', 'is there demand for this?', pre-PMF discovery. Do NOT activate when: the question is quantitative A/B testing on an existing product (use analytics), or the decision needs no customer input. More: deciqai.com/s/the-mom-test

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Before building, to test whether a problem is real and painful

    line 12
  2. Distinctive:

    When early "positive" feedback isn't converting to usage or revenue

    line 13
  3. Distinctive:

    Talk about their life, not your idea: Never mention the product first.

    line 17
  4. Distinctive:

    End with a real advance,: not a compliment: an intro, a pre-order, a follow-up meeting, access to data.

    line 22
  5. Distinctive:

    Only talking to friends/supporters.

    line 32

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

The Mom Test — Customer Interviews That Don't Lie to You

Overview

The Mom Test (Rob Fitzpatrick, 2013) is a way to talk to customers so that even your mom can't give you a false positive. The rule: ask about their life and past behavior, never about your idea. Compliments, hypotheticals ("would you buy?"), and pitch-then-ask all generate flattering noise founders mistake for validation. Good interviews collect facts about what people already do, pay for, and struggle with.

When to Use

  • Before building, to test whether a problem is real and painful
  • When early "positive" feedback isn't converting to usage or revenue
  • Choosing between problems/segments to pursue

The Process

  1. Talk about their life, not your idea. Never mention the product first. Ask what they're trying to get done and how they do it today.
  2. Ask about specifics in the past, not opinions about the future. "When did you last hit this problem? Walk me through it." not "Would you use X?"
  3. Dig for the three currencies of commitment: time, reputation risk, money. Real pain shows up as workarounds already paid for.
  4. Anchor vague claims to reality. "Always" → "how many times last month?" "I'd pay a lot" → "what do you pay now?"
  5. Shut up and listen. Talk <30% of the time. Gate: if you pitched or they complimented the idea, that data is contaminated → discard it.
  6. End with a real advance, not a compliment: an intro, a pre-order, a follow-up meeting, access to data. Gate: no advance offered = you learned nothing actionable → the interview failed.

Applying It Well

  • The best signal is an existing workaround they already spend on.
  • "That's interesting / I'd definitely buy that" = fluff; treat as zero.
  • Talk to people about a problem you can watch them have, not a demographic.

Red Flags

  • Leaving the interview happy (usually means you fished for compliments).
  • Feature requests taken literally instead of tracing the underlying problem.
  • Only talking to friends/supporters.

Verification

  • Idea was NOT mentioned until the end
  • Every claim anchored to a specific past instance
  • Existing workarounds + what they cost identified
  • A concrete commitment (time/reputation/money) requested

Part of deciqAI Knowledge Skills — 253 open-source thinking skills that make rigor executable for AI agents. The same skills power every deciqAI agent, which runs them autonomously to operate your company. See it run → https://www.deciqai.com/s/the-mom-test · Built by deciqAI · github.com/deciqAI · Contributions welcome.

Agents: latest version & machine-readable metadata → https://www.deciqai.com/s/the-mom-test.json

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.