SKILL FILE

Interview Guide Designer with AI

Design a discovery interview guide with the right questions to uncover real customer pain. Replaces leading questions with behaviour-based prompts that surface what users actually do.

Download Skill File ↓

What this skill file teaches Claude

Drop one markdown file into your repo. Claude Code learns how to run this entire workflow.

1

Behaviour-based question design

Every core question framed around past behaviour ("tell me about the last time you...") so you collect stories, not opinions.

2

Pain probes per question

Two or three follow-ups built in for every core question. Designed to surface frustration, workarounds, and emotional weight.

3

Anti-questions list

Explicit list of leading and hypothetical questions you should never ask, with why and what to ask instead. Stops nervous interviewers drifting into pitch mode.

4

Participant criteria

Must-haves, disqualifiers, and sample size so you don't waste cycles on interviews with the wrong people.

5

Call structure with time blocks

Suggested pacing for a 30 or 45 minute call so you don't run out of time before the good stuff.

6

What to listen for cheatsheet

Per-question signals to catch (workarounds, comparisons, emotional moments) so you know when to dig deeper.

What you can build with this

First discovery round on a new segment

You're about to talk to a new persona for the first time. Build a guide that tests your assumptions instead of confirming them.

Sharpen a weak interview script

Your last round of interviews felt flat. Rewrite the guide using behaviour-based prompts and pain probes.

Get the team interviewing consistently

Two PMs, three designers, one founder all running interviews. One shared guide so the signals are comparable.

Pre-launch validation

Before you build the next big feature, write an interview guide that tries to kill the idea, not validate it.

Get the full skill file

Everything above is 80% of the skill file. Download the complete version with full implementation details, agent prompts, and ready-to-run scripts.

Common questions

A good question asks about past behaviour, not future intent. "Tell me about the last time you tried to pick a CRM" works. "Would you use a CRM that..." doesn't. People are honest about what they did. They lie (politely) about what they would do. The Mom Test by Rob Fitzpatrick is the canonical reference here, and the question patterns in this skill are based on it.
Fewer than you think. A 30-minute call has room for five or six core questions plus follow-ups. A 45-minute call fits seven or eight. If your guide has 15 questions you're going to skim them and never get the deep answer. Cut ruthlessly. The best questions earn 5 to 10 minutes of conversation each.
Mostly yes. Consistency lets you compare signals across people. But evolve it after every 3 to 5 interviews based on what isn't working. Maybe a question keeps getting blank stares. Maybe one keeps surfacing something unexpected and deserves more follow-up. Treat the guide as a living document, not a fixed script.
Three rules. One: never mention your product or solution until after the core questions are done. Two: never use the word "would" in a question. Three: when they pause, stay silent for three seconds. The temptation to fill the silence with a leading prompt is huge. Resist it. The pause almost always produces the real answer.
If the segments are meaningfully different (different role, different stage of buying, different workflow), yes. If they're variations on the same buyer, one guide with a few branch questions is fine. The skill asks you to specify the segment up front so the questions land in their world, not a generic one.
It's not designed for that. Discovery interviews are about learning, sales calls are about qualifying. A discovery guide deliberately avoids pitching, which is bad sales technique. If you want to learn from your sales calls, run a separate dedicated discovery interview with a willing prospect, no pitch attached.

Ready to automate?

SoloStack gives you every skill pre-installed — scraping, marketing, sales, CRM, and more. One repo. Every department.

Book a Call →