write-interview-guide

Writes funnel-ordered, bias-linted user interview discussion guides from research questions.

1|Updated Jul 13, 2026
One-click install
npx skills add https://github.com/dineshrevunuru/SuperSkills --skill write-interview-guide-dineshrevunuru
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: write-interview-guide
Source: https://github.com/dineshrevunuru/SuperSkills/tree/main/write-interview-guide
Command: npx skills add https://github.com/dineshrevunuru/SuperSkills --skill write-interview-guide-dineshrevunuru

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Drafting interview questions from scratch produces leading, closed, or hypothetical questions that bias participants and yield unusable data. This Skill converts research questions into a piloted, semi-structured discussion guide using NN/g's 7-step process, so any interviewer can run sessions without leading participants. ## Core Features & Use Cases - 7-Step Guide Construction: Pulls research questions verbatim, brainstorms candidate questions, broadens closed questions, fills gaps, orders them into a funnel (warmup to sensitive), pre-writes neutral probes, and requires a pilot. - 7-Rule Lint Catalog: Detects and rewrites leading, closed-opener, double-barreled, prediction, rephrased-observation, jargon, and solution-fishing questions before the pilot. - Coverage Matrix: Maps every interview question back to research questions, enforcing at least two questions per research question and cutting orphans. - Use Case: A product team planning discovery interviews for a booking app hands you three research questions; the Skill outputs a 45-minute guide with 8 numbered questions, pre-written neutral probes, skip-if-short marks, a passing coverage matrix, and pilot notes. ## Quick Start Write a semi-structured interview discussion guide for these research questions about how users book salon appointments, including probes and a coverage matrix.

Frequently Asked Questions about write-interview-guide

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write user interview questions that are not leading?

Start with open openers like How, What, Tell me about, or Walk me through instead of Did/Was/Do/Would. Strip embedded premises and value judgments, ask about past real behavior rather than predictions, and run each question through a lint check for leading, double-barreled, and hypothetical phrasing.

How many questions should a 60-minute user interview have?

A 60-minute session holds roughly 8 to 12 main questions, since each question plus probes runs 3 to 5 minutes. Overstuffing eliminates probing time, so mark 2 to 3 questions as skip-if-short in advance.

What is a coverage matrix in an interview discussion guide?

A coverage matrix is a table mapping every interview question to the research questions it answers. Each research question needs at least two interview questions covering it, and any interview question mapping to nothing gets cut before the pilot.

When should I use a survey instead of a user interview?

Use a survey when the instrument is self-administered at scale rather than moderated live. Interviews suit exploratory questions needing probes and follow-ups; surveys suit quantifiable questions across many respondents, and each format has its own bias audit.

Why should I avoid asking users "would you use this feature"?

Prediction questions produce polite fiction because people cannot accurately forecast their own behavior. Ask about past real behavior instead, such as "Have you ever paid for something like this? Tell me about it," which yields recalled evidence rather than speculation.

Do I need to pilot an interview guide before the study?

Yes, no guide is done until piloted with a colleague or one real participant. The pilot checks total time, confusing questions, dead questions everyone answers identically, and awkward funnel ordering, and revisions are recorded in the guide header.