evidence-synthesis

Synthesize customer signals into attributed evidence sections for product initiatives and PRDs.

3|2|Updated Aug 24, 2026
One-click install
npx skills add https://github.com/hero-engine/hero --skill evidence-synthesis-hero-engine
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: evidence-synthesis
Source: https://github.com/hero-engine/hero/tree/main/domains/pm/skills/evidence-synthesis
Command: npx skills add https://github.com/hero-engine/hero --skill evidence-synthesis-hero-engine

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Product bets often fail the "how do you know?" challenge because evidence is aggregated into unsourced claims, quotes get paraphrased, and counter-evidence is quietly dropped. This Skill provides the rules for building Evidence sections on initiatives, PRDs, and intake investigations that preserve source attribution, verbatim quotes, and honest counter-evidence. ## Core Features & Use Cases - Evidence pyramid ranking: Classifies signals by trust tier, from verbatim customer quotes down to internal hunches, and requires each Evidence section to name its tier. - Attribution-preserving aggregation: Rolls up evidence across many linked intakes by summarizing counts while keeping per-source links and verbatim quotes intact. - Synthesize-then-compare discipline: Structures agent synthesis as a proposed reading that the PM reconciles against their own independent read, with theme-to-verbatim links preserved. - Use Case: When promoting 12 intake tickets about SAML requests into a single initiative, use this Skill to generate an Evidence section that shows the aggregate count, lists each source intake with its verbatim quote, separates interpretation into the Bet section, and includes a counter-evidence subsection naming the segment where the bet does not hold. ## Quick Start Ask the agent to synthesize the linked intakes for an initiative into an Evidence section with verbatim quotes, source attribution, and a counter-evidence subsection.

Frequently Asked Questions about evidence-synthesis

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

FAQPage Schema
How do I write an evidence section for a product initiative?▼

Lead with verbatim customer quotes carrying source links, then add discovery synthesis, usage data, and a counter-evidence subsection. Summarize aggregate counts but preserve per-source attribution so reviewers can trace every claim back to its intake, interview, or dashboard.

How to aggregate customer feedback across multiple intake tickets?▼

Summarize the count to make the pattern visible, but list each source intake with its verbatim quote so trust remains verifiable. Aggregates without underlying sources are claims, not evidence, and fail the "how do you know?" challenge.

What counts as strong evidence for a product bet?▼

Verbatim customer quotes rank highest, followed by interview synthesis preserving direct quotes, then usage-data signals, then NPS comments. Internal hunches are questions to investigate, not evidence. Each Evidence section should name which tier its signals come from.

Should AI synthesis replace the PM's own reading of interviews?▼

No. Use the synthesize-then-compare loop: the agent proposes themes with verbatim quotes attached, the PM forms an independent read, and the two passes are reconciled. A synthesized theme stays "proposed pending PM review" until the human reconciles it.

Why include counter-evidence in an initiative spec?▼

Counter-evidence forces the team to confront the strongest argument against the bet, signals the analysis was honest rather than selective, and surfaces boundary conditions like segments where the bet does not hold. An Evidence section with no counter-evidence subsection is suspicious.

When should customer feedback be labeled as paraphrased instead of quoted?▼

Label as paraphrased whenever the original signal is not a direct quote, such as a support ticket summary or sales note, and link the source. Never invent a quote or present paraphrased text as verbatim, since the trust signal lives in the customer's own words.