Back to Skills
Discovery/research-synthesis-engine

Research Synthesis Engine

Synthesize multiple research sources into coherent insights with clear evidence chains.

Time Saved

8+ hrs → 1 hr

Compared to doing it manually

Slash Command

/research-synthesis-engine

Type this in Claude to run the skill

The Problem

Research insights live in scattered docs, slides, and people's heads. When you need evidence, you can't find it. Decisions get made without the full picture.

What You Get

  • ✓Cross-source pattern detection
  • ✓Theme clustering with evidence strength
  • ✓Convergence and contradiction analysis
  • ✓Research gaps identified
  • ✓Prioritized opportunity list
  • ✓Atomic insight database

Want this automated?

This skill is part of 2 workflows that automate multiple steps together:

Batch Interview Synthesis

Agent Workflow

10 interviews. 15 minutes. Done.

4 skills automated
7-10 hrs → 15 min

VoC Analysis

Agent Workflow

Tame the feedback firehose.

3 skills automated
3 hrs → 30 min

How to use this skill

  1. 1Download the skill file using the button on this page
  2. 2Add the file to your .claude/skills/ folder in your project
  3. 3Type /research-synthesis-engine in Claude to run the skill

Best For

Research sprintsQuarterly reviewsBusiness casesStrategy development

Related Skills

JTBD Extractor

/jtbd-extractor

Extract Jobs-to-be-Done statements from research data to uncover innovation opportunities.

User Interview Analyzer

/user-interview-analyzer

Transform interview transcripts into structured insights with quotes, patterns, and recommendations.

Feedback Categorizer

/feedback-categorizer

Analyze and categorize customer feedback into actionable themes using affinity mapping.

App Review Analyzer

/app-review-analyzer

Extract themes, complaints, and feature requests from app reviews at scale.

Frequently Asked Questions

Research synthesis combines findings from multiple research activities (interviews, surveys, analytics) into coherent insights. It identifies patterns, contradictions, and key takeaways that inform product decisions.

Use affinity mapping: write insights on sticky notes, group related ones, identify themes. Look for patterns across sources. Distinguish between what users say, what they do, and what they need.

Lead with insights, not methodology. Use the format: "We learned [insight] which means [implication] so we should [recommendation]." Include supporting quotes but don't overwhelm with data.

View Workflow →