Files
pm-claude-skills/skills/user-interview-synthesis/SKILL.md
T
mohitagw15856 f3b9d008fe feat: 100 skills milestone — 7 new skills + quality improvements across all 93
New skills added:
- teaching-lesson-plan: structured lesson plans for any subject/audience/setting
- seo-content-brief: complete SEO briefs with intent, competitor gaps, and outline
- media-pitch: story-first journalist pitches with angle development framework
- change-management-plan: stakeholder analysis, comms strategy, adoption metrics
- workshop-facilitation-guide: activity instructions, decision protocols, facilitator moves
- sales-forecasting-model: pipeline model, scenario analysis, assumption log
- tax-planning-checklist: year-end tax planning across income, pension, CGT, reliefs

Quality improvements across all 93 existing skills:
- Standardised description format: "Verb the thing. Use when X. Produces Y."
- Added Required Inputs section to all skills missing it (prompts for missing info)
- Added Quality Checks section to all skills missing it (specific, not generic)
- Fixed broken multiline YAML descriptions
- Removed non-standard frontmatter keys (tool_integration, metadata blocks)

README updated to v6.0.0 with 100-skill count, new skill tables, and article series

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
2026-04-20 20:52:31 +01:00

2.3 KiB

name, description
name description
user-interview-synthesis Synthesise user interview transcripts into structured research findings. Use when asked to analyse interview notes, synthesise qualitative research, identify themes from user interviews, or turn raw interview data into actionable product insights. Produces a themed synthesis with supporting quotes, 'so what' implications, and recommended next steps.

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]

[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")