user-interview-synthesis
This skill transforms raw interview transcripts into structured research synthesis by identifying recurring themes, extracting supporting quotes, and deriving product implications. Use it when analyzing user interview notes, synthesizing qualitative research data, identifying patterns across participant responses, or converting interview findings into actionable product insights. The output includes themed summaries with verbatim quotes from at least three participants, "so what" implications for product decisions, and recommended next steps.
git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills /tmp/user-interview-synthesis && cp -r /tmp/user-interview-synthesis/plugins/pm-discovery/skills/user-interview-synthesis ~/.claude/skills/user-interview-synthesisSKILL.md
# User Interview Synthesis Skill Transform raw interview transcripts into a structured synthesis document that surfaces themes, pain points, and actionable insights. ## Required Inputs Ask the user for these if not provided: - **Interview transcripts or notes** (even rough notes work) - **Number of participants and their profiles** (role, company size, context) - **Research questions** (what was the study trying to answer?) - **Date range** of research (for context) ## Process 1. Read all provided transcripts fully before drawing conclusions 2. Identify recurring themes (minimum 3 mentions to qualify as a theme) 3. Categorize findings into: Pain Points, Workflow Insights, Feature Requests, Delight Moments 4. Select 2-3 verbatim quotes per theme that best represent the pattern 5. Draft "So What" implications for each theme — what does this mean for the product? 6. **Validate** — Confirm every theme has quotes from at least 3 participants. Flag any insight resting on fewer as low-confidence. ## Output Structure ### Research Synthesis: [Study Name] **Participants:** [n] **Date Range:** [dates] **Research Questions:** [list] #### Theme 1: [Theme Name] - Summary (2-3 sentences) - Supporting quotes (from at least 3 participants) - Implication for product [Repeat for each theme] #### Low-Confidence Signals (1-2 participants only) [Findings worth tracking but not acting on yet — note what further research would confirm or deny] #### Recommended Next Steps [Specific, actionable recommendations based on findings] ## Quality Checks - [ ] Every theme is supported by quotes from at least 3 participants - [ ] Implications connect to specific product decisions, not just observations - [ ] Researcher bias check: no leading language, findings don't all support one hypothesis - [ ] Single-source signals are flagged separately, not mixed into main themes - [ ] Research questions from the study brief are each addressed (even if the answer is "inconclusive") ## Anti-Patterns - [ ] Do not mix single-source signals into main themes — insights cited by only one participant must be flagged separately - [ ] Do not write implications that are observations restated rather than product decisions enabled - [ ] Do not include themes that only support the project hypothesis — contradictory findings must be surfaced, not omitted - [ ] Do not present findings without quotes — every theme requires verbatim evidence from at least 3 participants - [ ] Do not leave research questions unanswered — each question from the study brief must be explicitly addressed, even if the answer is inconclusive
Design a 360-degree feedback survey or write a structured 360 feedback report. Use when asked to build a 360 feedback process, write 360 feedback for a colleague, design a feedback survey, or produce a feedback report. Produces either a complete survey instrument with rating scales and open-ended questions, or a structured narrative feedback report with themes, strengths, and development areas.
Decode a 401k or workplace retirement plan — the real cost of its funds, the match's fine print, vesting math, and the plan features worth using or avoiding. Use when someone asks 'is my 401k any good', 'decode my 401k plan', 'which funds should I look at', or 'what fees am I paying'. Produces a fee decode in dollars-over-time, match and vesting math, a fund-lineup triage by cost, and the questions for HR or the plan administrator.
Design statistically rigorous A/B tests for product features, UI changes, onboarding flows, and pricing experiments. Use when asked to set up an experiment, design an A/B test, calculate sample size, or interpret test results. Produces a complete test plan with hypothesis, variant definitions, sample size, duration estimate, guardrail metrics, and a results interpretation guide.
Analyse a finished A/B test and write the readout — the result, whether it's statistically and practically significant, what it means, and the ship/no-ship call. Use when asked to analyse experiment results, write an A/B test readout, interpret test data, or decide whether to ship a variant. Produces a clear verdict with the lift and confidence, segment cuts, the risks (peeking, novelty, sample), and a recommendation. Distinct from planning a test — this reads results.
Generate a WCAG 2.2 accessibility audit checklist and remediation suggestions for any UI or design. Use when asked to audit for accessibility, check WCAG compliance, review a design for a11y issues, or create an accessibility remediation plan. Produces a prioritised checklist with pass/fail assessments and specific fixes.
Plan a trip that actually works with a disability or access need — confirm real accessibility (not just 'accessible' labels), book the assistance in advance, plan for equipment and medication, and build in the contingencies for when access breaks down. Use when someone says 'plan an accessible trip', 'travelling with a wheelchair/disability', 'book assistance for my flight', or 'will this hotel actually work for me'. Produces an access-verified itinerary, an assistance-booking checklist, an equipment/medication plan, and contingency scripts. Verify specifics with providers.
Request a reasonable accommodation at work or in education — frame it around the barrier and the adjustment (not your diagnosis), cite the right process, and navigate the back-and-forth constructively. Use when someone says 'I need a workplace accommodation', 'request reasonable adjustments', 'ADA/Equality Act accommodation', or 'how do I ask for accommodations for my disability/condition'. Produces the request letter, a barriers-and-adjustments map, disclosure guidance, and a plan for the interactive process. Not legal advice — routes to the formal process and to advocacy where needed.
Build a structured account plan for any key customer or target account. Use when asked to create an account plan, key account strategy, strategic account review, or territory plan. Produces a complete account plan with relationship map, growth opportunities, risks, and 90-day action plan.