Menu

Individual skill

interview-guide-builder

0upvotes

Writes a non-leading user-research discussion guide with warm-up flow, open core questions, an attached probe bank, time budgets, and a pre-field bias audit. Use when someone asks "write my interview guide", "what should I ask users in discovery interviews", "review my questions for leading language", or is preparing generative or evaluative user interviews. Do NOT use for hiring-loop questions with competencies and scoring anchors - use interview-question-kit instead. Do NOT use for sourcing deep domain knowledge from subject-matter experts with laddering - use expert-interview instead. To analyze the notes afterward, use interview-synthesis.

skills/interview-guide-builder/SKILL.md

Read pinned source

Source commit 97a13607d669157a4a16d5ba79b77f208319f7b9

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Instructions only
Last checked
Nov 11, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
24
Repository last updated
Oct 13, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Interview Guide Builder

A discussion guide is scaffolding, not a script: it keeps the researcher oriented while leaving room for the participant to lead. The costly failure it prevents is manufactured confirmation - a guide full of leading questions returns exactly the answers the team already believed, and the product ships into a market that was never actually heard.

## Operating procedure

### Step 1: Gather inputs

Collect before drafting:

- Research goal in one sentence, and whether the round is **generative** (understand behavior and needs) or **evaluative** (react to a concept or prototype). Default: generative.
- The 3-5 things the team must learn - these become topic blocks; anything beyond five gets cut or deferred to another round.
- Session length (default 60 minutes), participant profile, and whether sessions are recorded.
- The team's current hypotheses - written down explicitly so they can be kept OUT of the question stems.
Back to top