Index of every page on this site: llms.txt
All skills
deanpeters avatar

/research-synthesis

@476ae12
Run it yourself

Turn raw interview notes and feedback into themes, insights, and opportunity statements. Use when you have a pile of research and need to know what it says before deciding anything.

Use this Skill: https://skilld.dev/gh/deanpeters/product-manager-skills/research-synthesis

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

template.md

≈463 tokens on demand. Your agent reads this file only when SKILL.md points to it.

Research Synthesis Template

Every quote, count, and participant traces to the supplied notes, or is [NEEDS SOURCE]. Quality checks at the bottom.


1. Research frame

Question: · Participants (role, segment, how chosen, N): · Sessions / sources: Hypotheses held going in (written before coding): 1.

2. Coded observations (excerpt)

# Participant Observation (their words) Unprompted? Contradicts a hypothesis?

3. Themes (affinity groups)

Theme (customer's words) Participants N of total Strength (unprompted / emotional / only when asked)

4. Insights

# Insight (labeled as interpretation) Evidence (quotes + participants) N of total Confidence (strong / suggestive / thin)

Insight check: specific · evidenced · decision-relevant · no solution inside.

5. Opportunity statements (needs, no solutions)

# "I need to..." (customer's words) From insight # Ideas heard (kept separate)

6. Contradictions

Observation Cuts against (hypothesis or insight #) What it changes

7. What the research does not show

  • Who we did not hear from:
  • Questions nobody answered:
  • Claims resting on one voice:
  • What this sample cannot speak to:

8. Next

[Handoff: opportunity tree / more interviews / assumption mapping]


Quality checks

  • Hypotheses were written before coding
  • Every insight traces to quotes and a count
  • Counts are participants (6 of 8), not percentages of a market
  • Observation, interpretation, and opinion are kept apart
  • No solution sits inside an opportunity statement
  • Contradictions are listed and read
  • A gaps list exists
  • Nothing invented: quotes, counts, and participants all trace to the notes

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

1 warning7d3 checks · Risk SAFE
  • Gen Agent Trust Hub7d

    The skill provides a structured workflow for research synthesis but possesses an inherent attack surface for indirect prompt injection due to the processing of untrusted external research data.

  • Socket7d

    No alerts

  • Snyk7d

    Risk: MEDIUM · 1 issue

Signed by skilld at 476ae12. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub last week.

Activeupdated last week
argument-hint
[the research you have: interview notes, tickets, survey comments]
type
workflow
theme
discovery-research
Other metadata
intent
Take research that is still raw (interview notes, call transcripts, tickets, survey comments) and walk it through coding, affinity grouping, insight writing, and opportunity framing, with every insight traced to the notes behind it and every claim sized by how many people said it. Ends with opportunity statements ready for an opportunity solution tree, and a list of what the research does not show.
best_for
[
  "Making sense of 5 to 30 interviews before anyone proposes a solution",
  "Separating what customers did and said from what the team concluded",
  "Producing opportunity statements that trace back to evidence",
  "Showing a stakeholder what the research does and does not support"
]
scenarios
[
  "I ran eight dispatcher interviews and have a folder of notes. What do they say?",
  "Support tickets and interviews seem to disagree. Help me sort what's real",
  "Turn these plant-visit notes into opportunities for the roadmap discussion",
  "Leadership wants the insight in one page; I want it traceable"
]
estimated_time
45-90 min

README badge

README badge for deanpeters/product-manager-skills/research-synthesis