Skip to content
Beta Multi-model support (OpenAI, Gemini, and more) launching soon.
RBA RBA Skills

stakeholder-interview-guide

Installable Ships in envision-toolkit — or copy the raw skill below.
Open Claude.ai

Paste into Claude Code, Claude.ai, the desktop app, or the browser extension — ⌘/Ctrl+V.

ExperimentalNo security review

Stakeholder Interview Guide

Produce a conversational, comparable interview guide for a single stakeholder type in an RBA Envision engagement. Good guides open doors rather than close them: open-ended primary questions, built-in follow-up prompts to rescue flat answers, and a synthesis-notes section authored before the interview so it can be filled in while memory is fresh.

When this skill applies

  • User is in (or about to start) the Envision discovery phase and needs interview questions
  • User names a stakeholder role or type ("clinical ops manager", "content authors", "IT director")
  • User asks for a "discussion guide", "interview guide", or "discovery questions"
  • User wants consistent, comparable questions across several interviews

Skip when: the user wants to analyze completed interviews (that is synthesis, downstream), or wants a deck (project-kickoff-deck, envision-findings-deck).

Inputs

Collect these before generating. Ask for any that are missing — do not invent the objective or topics.

Input Required Description Example
Project Yes Engagement name Primary Care UX and Strategy
Stakeholder type / role Yes The type of interviewee, not a named person Clinical Operations Manager or End user — nurse care coordinator
Objective Yes One sentence: what you need to learn from this type Understand pain points in the patient intake workflow and what a better experience looks like
Topics Yes 3-5 themes to explore, semicolon-separated Current workflow; pain points; workarounds; what good looks like; tech constraints
Duration No (default 45m) Interview length 45 minutes
Interviewer No RBA person running it Kassie Gibbons

Workflow

Step 1 — Confirm scope and the one-guide-per-type rule

Restate the stakeholder type and objective back to the user. If they list multiple distinct roles (e.g., a nurse and a department director), tell them those need separate guides and confirm which one to build first. One guide serves every interviewee of the same type.

Step 2 — Derive themes from the objective

Turn the supplied topics into 3-5 named thematic sections that ladder up to the objective. Each theme must be answerable in 5-8 minutes so the core block fits the duration. Name themes in plain language (e.g., "How intake works today", not "Current-state process taxonomy").

Step 3 — Write one open-ended primary question per theme

Lead every theme with a narrative opener — "Walk me through…", "Tell me about…", "Describe the last time…". Never a yes/no question. Attach 3-5 follow-up prompts per theme drawn from the universal rescue set in templates.md (specific example / what happens next / how often / who else / what would need to be true).

Step 4 — Assemble the full guide structure

Follow the fixed section order in templates.md:

  1. Header block (project, interviewee, date, interviewer, objective)
  2. Pre-interview checklist
  3. Introduction script + 1-2 warm-up questions
  4. Core questions (the themed sections from Steps 2-3)
  5. Standard closing questions
  6. Synthesis-notes table + top-3 takeaways + cross-interview connections + open questions

The introduction script must include a recording/notes permission ask. The closing must keep the "is there anything I didn't ask?" question.

Step 5 — Pre-author the synthesis section

The synthesis-notes table is part of the deliverable, not an afterthought. Build it empty and ready so the interviewer fills it in within minutes of the interview ending.

Step 6 — Export to a branded Word doc

Write the guide to <project-slug>-<role-slug>-interview-guide.md as the working draft, then state how to produce the branded .docx: paste the guide into Claude in Word against the RBA Word template so fonts, colors, and logo apply automatically. Do not duplicate brand tokens here — reference resources/rba-design-system.md if the doc leaves the template.

Step 7 — Quality check before returning

Confirm against the quality bar below, then return the guide and remind the user to run a brand-voice pass before sending the calendar invite + guide to participants.

Output format

A single Word-ready guide (markdown working draft → branded .docx) containing, in order: header block, pre-interview checklist, introduction + warm-up, 3-5 themed core sections each with one primary question and follow-up prompts, standard closing questions, and a pre-built synthesis-notes section. Full skeleton lives in templates.md.

Quality bar

  • One guide per stakeholder type, never per individual.
  • Zero yes/no primary questions — every theme opens with a narrative prompt.
  • Every primary question has at least three follow-up prompts.
  • Core block timing fits the stated duration (themes × 5-8 min + intro + closing).
  • The introduction includes an explicit recording/notes permission ask.
  • The closing retains "Is there anything I didn't ask that's important?" and "Who else should we talk to?".
  • The synthesis-notes section is present and empty-ready before the interview.
  • No personal names are baked into a reusable guide — it is keyed to the role.

Reference and template files

  • templates.md — the fixed guide skeleton, the interview-theme patterns, the universal follow-up-prompt set, and the synthesis-notes table.
Technical details
Plugin
envision-toolkit
Author
Kassie Gibbons
Skill name
stakeholder-interview-guide
Maturity
experimental
Security review
No security review
Owners
  • strategy
Argument hint
[--project NAME] [--role "stakeholder type"] [--objective "what to learn"] [--topics "theme; theme; theme"] [--duration 45m] [--interviewer NAME]
Allowed tools
  • Read
  • Write
  • Edit
  • Glob
Source
plugins/envision-toolkit/skills/stakeholder-interview-guide/SKILL.md

Edit this skill on GitHub — opens GitHub's web editor. No git knowledge needed.