Menu

Individual skill

interview-synthesis

0upvotes

Turns raw interview notes into themed, evidence-tagged insights via a two-pass affinity-mapping procedure, with frequency and confidence ratings and stakeholder-ready quotes. Use when someone asks "synthesize these interviews", "what themes came out of our research round", "turn these transcripts into findings", or has finished a qualitative round and needs actionable output. Do NOT use for synthesizing published papers or mixed documents - use research-synthesis instead. Do NOT use for building the personas themselves - use user-persona instead. Do NOT use for consolidating hiring-interview scorecards - use interview-debrief-synthesizer instead.

skills/interview-synthesis/SKILL.md

Read pinned source

Source commit 97a13607d669157a4a16d5ba79b77f208319f7b9

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Not checked yet
Last checked
Nov 6, 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 Synthesis

Synthesis is where data becomes insight. The job is not to summarize what people said - it is to identify the underlying pattern that explains why they said it and what it means for design or strategy. The costly failure it prevents is the highlight reel: a deck of cherry-picked quotes that confirms what the team already believed, laundered through the word "research."

## Operating procedure

### Step 1: Gather inputs and check the dataset

Collect: the transcripts or structured notes, the original research questions, and who the findings are for (design team vs. executives changes the framing, not the rigor). Enforce the data rules:

- Every interview needs a cleaned transcript or structured notes with participant ID, date, and verbatim quotes marked. Do not synthesize from memory or from the researcher's paraphrase alone.
- **Minimum viable dataset: 5 interviews** for foundational themes. Fewer is workable only with an explicit low-confidence label on every finding.
- **Check for saturation**: if the last 3 interviews produced no new themes - only more evidence for existing ones - the round has reached saturation and the theme set can be treated as stable. If new themes were still appearing in the final interviews, say so and flag that more interviews would likely surface more; the synthesis is a snapshot, not the territory.