In the Skill's Own Terms
Synthesizes raw user research into a structured markdown document: themes with prevalence counts and participant quotes, an insight-to-opportunity table scored by impact and effort, user segments, prioritized recommendations, open questions and methodology notes. It accepts interview transcripts, survey results (CSV or pasted), usability test notes or recordings, support tickets, NPS/CSAT responses and app store reviews, and is invoked as /research-synthesis with the data as arguments.
Optional connectors to user feedback, product analytics and a knowledge base let it pull support tickets, validate qualitative findings with usage data and publish the synthesis to a research repository. Research methods and interview guides live in the separate user-research skill.
What it produces
- A markdown synthesis document titled Research Synthesis with the study name.
- A Key Themes section where each theme states its implication for the product.
- An insight-to-opportunity table with impact and effort columns.
- A user segments table listing characteristics, needs and rough size.
How It Works
- 01Pass the Research as the Argument
The command takes the research data, transcripts or survey results as its argument string, so the material you supply is what gets synthesized.
- 02Fill in the Study Header
Every synthesis opens by stating the method, the participant count, the date range and the researcher, so the reader knows what the findings rest on.
- 03Lead with a Short Executive Summary
Three to four sentences carrying the key findings, placed before any of the detail.
- 04Group Findings into Named Themes
Each theme gets a name and a one-line summary of what it is about, then supporting quotes underneath.
- 05Define the User Segments
A dedicated section names the segments the data reveals, separated from the theme list.
- 06Close by Naming What Is Still Unknown
The document ends by listing the questions the study did not answer, which becomes the starting point for the next round of research.