synthesize-research-data

Synthesize qualitative research data into traceable themes, insights, need statements, and HMW questions.

1|Updated Jul 13, 2026
One-click install
npx skills add https://github.com/dineshrevunuru/SuperSkills --skill synthesize-research-data-dineshrevunuru
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: synthesize-research-data
Source: https://github.com/dineshrevunuru/SuperSkills/tree/main/synthesize-research-data
Command: npx skills add https://github.com/dineshrevunuru/SuperSkills --skill synthesize-research-data-dineshrevunuru

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Raw research data — interview transcripts, field notes, diary entries, open survey text — often gets reduced to cherry-picked quotes, invented percentages, or vague themes that cannot be traced back to evidence. This Skill turns raw qualitative (and mixed qual+quant) data into defensible findings by enforcing traceability, a mandatory disconfirming-case hunt, honest prevalence counts, and calibrated confidence levels. ## Core Features & Use Cases - Situational approach selection: Routes to thematic coding, affinity diagramming, framework-mapping (JTBD/journey/matrix), or mixed qual+quant synthesis based on the decision, data, and problem shape — never one fixed pipeline. - Rigor constants: Enforces source-tagged traceability, a mandatory disconfirming-case hunt before accepting any theme, prevalence as "X of Y" (never bare percentages), a High/Med/Low confidence level per finding, and reporting of negative cases. - Define-stage outputs: Produces linted user need statements and How-Might-We questions built only on High/Med-confidence insights, each tied to a decision and a metric. - Use Case: You have 11 interview transcripts from a chatbot beta test. The Skill atomizes the data, catches that a vivid "users love auto-booking" quote is only 2 of 11 participants, and produces a High-confidence finding (6 of 11 need a confirm-and-undo step) with a need statement and HMW question. ## Quick Start Synthesize these interview transcripts into themes, insights, need statements, and How-Might-We questions with evidence counts and confidence levels.

Frequently Asked Questions about synthesize-research-data

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I synthesize user interview transcripts into themes?

Atomize each transcript into single observations with source tags, then pick an approach: thematic coding for open questions, framework-mapping when a JTBD or journey frame fits, or affinity diagramming for team sessions. Run a disconfirming-case hunt before accepting any theme.

What is the difference between thematic coding and affinity diagramming?

Thematic coding suits large solo corpora (5+ transcripts) where traceability to quotes matters most. Affinity diagramming suits team sessions with up to roughly 200 observations where shared ownership and buy-in are the priority.

Can I report percentages from qualitative research?

No. Report prevalence as counts like "6 of 8 participants," never as percentages. A small qualitative sample licenses existence and texture claims, not population prevalence rates, and percenting qual data is an over-claim.

How do I write a good How-Might-We question from research?

Use the format HMW + help/enable/let + specific user + achieve outcome + in context, traceable to a need statement. It must name no UI component, allow at least five visibly different solutions, and frame the desired outcome rather than restating the pain.

When should I not use qualitative synthesis for research data?

Do not use it for usability-test findings with severity ratings, statistical claims from large samples, or A/B test analysis. Those belong to usability analysis and quantitative evidence methods; this skill handles interviews, field notes, diaries, and open survey text.