interview-plan
Turn a brief, data, or desk research into a customer interview plan: research questions, screener, guide, and a note format. Use when someone is about to talk to customers and needs to decide who to recruit, what to ask, and when to stop.
superhero-tech · 已有静态检查记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add superhero-tech/superhero-skills --skill interview-plan技能说明
name: interview-plan description: "Turn a brief, data, or desk research into a customer interview plan: research questions, screener, guide, and a note format. Use when someone is about to talk to customers and needs to decide who to recruit, what to ask, and when to stop." metadata: ready_to_publish: "true"
Interview Plan
Build a customer interview plan gate by gate from evidence the team already has: research questions tied to a decision, a screener, a guide made of topics and probes, and a note format that drops straight into affinity mapping.
Respond and produce all artifacts in the user's conversation language. Mirror the vocabulary from the user's project files.
This skill plans interviews. It does not run them, does not invent participants or answers, and does not synthesize results - that is affinity-mapping.
Where this sits
desk-research (competitors / industry) ─┐
├─→ interview-plan → affinity-mapping → ost-builder
data-analysis (your own quant data) ─┘
Either input alone is optional. Having some evidence base is not.
Reference load map
Load each file only at the stage indicated:
| Stage | Load |
|---|---|
| 2 Recruiting | references/screener.md |
| 3 Guide | references/question-craft.md + references/modes.md |
| 4 Logistics | references/sample-and-consent.md |
| 5 Artifacts | assets/plan-template.md, assets/guide-template.md, assets/notes-template.md |
Hard rules (always active)
- No evidence base, no plan. A brief, quantitative data, or existing qualitative material must be present. Without one, stop at Stage 0 and say what is missing. A plan invented from nothing produces questions that test the team's imagination.
- Every guide question traces to a research question. No mapping, no question.
- Mom Test lint on every question. Banned: hypothetical and future-tense ("would you", "how much would you pay"), solution-first (mentions your product before a story exists), compliment bait, leading, yes/no, double-barrelled. See
references/question-craft.md. - The falsifier is mandatory. The plan states what the team would have to hear to conclude its hypothesis is wrong, and the guide contains at least one question capable of producing exactly that.
- Open before specific. Broad story prompts come first; named topics later. A topic raised by the interviewer is not evidence that it matters.
- Verbatim or it did not happen. Plan for a recording or a transcript, one file per interview, participant IDs assigned upfront.
affinity-mappingcannot work without verbatim quotes and sources. - Never fabricate participants or answers. Synthetic respondents are sycophantic and untraceable to any real conversation. If the user wants practice, produce a roleplay explicitly labelled as an exercise, never as data.
- The user never picks a methodology. You choose the spine (Stage 3.1) and say why in one sentence. Asking "story-based or switch interview?" pushes a decision onto someone who hired the skill to make it.
Lazy user mode
Only after an actual skip signal from the user ("skip", "", "." or equivalent) - never as a default reading of a short request: auto-decide, state your pick and why in one sentence, continue. Exception: the falsifier (1.5) is never auto-skipped - it is the one thing protecting the plan from confirming what the team already believes. If the user will not answer it, derive a candidate from their hypothesis and make them approve or edit it. If they skip that too, write the candidate into the plan tagged falsifier: derived, unconfirmed and repeat the tag in the wrap-up - a gate nobody confirmed stays visible rather than silently passing.
Workflow
Stage 0 Setup → 1 Decision + questions + falsifier → 2 Recruiting → 3 Guide → 4 Logistics → 5 Artifacts
A gate ends your turn. Present the block, ask, and stop there - do not open the next stage in the same message, and never produce artifacts before the last gate has an answer. Showing a gate and walking through it yourself is the same as having no gate. Generate everything in one pass only when the user asks for that explicitly ("just give me the whole plan"); say once that the gates were skipped and which decisions you made alone.
Stage 0 - Setup and evidence base
- Ingest in two passes. First take inventory: list the
.mdfiles at the project root and inresearch/,analyses/or similarly named folders, each with its first heading. Names alone lie, and briefs, PRDs and ICP notes rarely follow a convention - but reading everything burns the context on unrelated documentation. Then read in full only what the inventory shows is about the customers, the decision, or the domain. Above roughly 15 candidates, show the inventory and ask which to read. Note.csv/.xlsxfilenames and data dictionaries without opening them;ost-state.jsonread-only; list transcripts already present. - Report the base in one table -
source | what it gives | how the plan will use it. A source whose third column you cannot fill is not a source; drop it from the table. What survives is the citation pool for Stage 2. - The base is empty when nothing in it says who the customers are or what decision is at stake - a folder of files about something else counts as zero, not as two. Then stop and ask for the minimum; a paragraph is enough. Write that answer to
interviews/brief.mdas source zero and tag everything derived from it[stated, unverified], so Stage 2's citation rule stays honest instead of being quietly skipped. - If
interviews/plan.mdexists: offer revise / plan a new round / stop.
Stage 1 - Decision, research questions, falsifier (gate)
- Decision at stake - one sentence: what gets approved, rejected, or changed by what we hear. When the brief already names the solution, the decision at stake is not that solution - it is w