Stats
Actions
Tags
From design
Synthesize user research into themes, insights, and recommendations
How this command is triggered — by the user, by Claude, or both
Slash command
/design:research-synthesis <research data, transcripts, or survey results>The summary Claude sees in its command listing — used to decide when to auto-load this command
# /research-synthesis > If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](../CONNECTORS.md). Synthesize user research data into actionable insights. See the **user-research** skill for research methods, interview guides, and analysis frameworks. ## Usage ## What I Accept - Interview transcripts or notes - Survey results (CSV, pasted data) - Usability test recordings or notes - Support tickets or feedback - NPS/CSAT responses - App store reviews ## Output ## If Connectors Available If **~~user feedback** is connected: - Pull suppor...
If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md.
Synthesize user research data into actionable insights. See the user-research skill for research methods, interview guides, and analysis frameworks.
/research-synthesis $ARGUMENTS
## Research Synthesis: [Study Name]
**Method:** [Interviews / Survey / Usability Test] | **Participants:** [X]
**Date:** [Date range] | **Researcher:** [Name]
### Executive Summary
[3-4 sentence overview of key findings]
### Key Themes
#### Theme 1: [Name]
**Prevalence:** [X of Y participants]
**Summary:** [What this theme is about]
**Supporting Evidence:**
- "[Quote]" — P[X]
- "[Quote]" — P[X]
**Implication:** [What this means for the product]
#### Theme 2: [Name]
[Same format]
### Insights → Opportunities
| Insight | Opportunity | Impact | Effort |
|---------|-------------|--------|--------|
| [What we learned] | [What we could do] | High/Med/Low | High/Med/Low |
### User Segments Identified
| Segment | Characteristics | Needs | Size |
|---------|----------------|-------|------|
| [Name] | [Description] | [Key needs] | [Rough %] |
### Recommendations
1. **[High priority]** — [Why, based on which findings]
2. **[Medium priority]** — [Why]
3. **[Lower priority]** — [Why]
### Questions for Further Research
- [What we still don't know]
### Methodology Notes
[How the research was conducted, any limitations or biases to note]
If ~~user feedback is connected:
If ~~product analytics is connected:
If ~~knowledge base is connected:
npx claudepluginhub vishbin/knowledge-work-plugins-v --plugin design