research-synthesis

Synthesize mixed discovery evidence into durable research files with job verdicts.

Updated Jul 10, 2026
One-click install
npx skills add https://github.com/subvisual/the-a-team --skill research-synthesis-subvisual
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: research-synthesis
Source: https://github.com/subvisual/the-a-team/tree/main/.claude/skills/research-synthesis
Command: npx skills add https://github.com/subvisual/the-a-team --skill research-synthesis-subvisual

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Discovery evidence arrives fragmented across interview notes, survey comments, support themes, transcripts, and analytics summaries, making it hard to produce a coherent input for discovery and PRD work without losing contradictions or overstating certainty. ## Core Features & Use Cases - Evidence Synthesis: Normalize mixed sources, surface converging themes, contradictions, and gaps, and label evidence strength qualitatively (Strong, Moderate, Directional, Unknown). - Job Verdicts & New-Job Signals: Render a supports/challenges/suggests-refinement verdict per active JTBD with cited evidence, and record raw new-job signals routed to the jobs-to-be-done skill. - Durable Artifacts: Write append-only synthesis files to docs/product/research/<date>-<slug>.md with a sources frontmatter, plus a context.md digest and [conflict] ledger entries. - Use Case: After six admin interviews, a support-tag summary, and funnel analytics, produce one synthesis showing permission hesitation as the top theme, a refinement verdict on the onboarding job, and discovery questions to carry forward. ## Quick Start Synthesize the un-ingested batches in docs/product/input/ into a research synthesis answering why first-time admins abandon workspace setup.

Frequently Asked Questions about research-synthesis

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

FAQPage Schema
How do I synthesize user research from multiple sources?▼

Gather interview notes, survey themes, support patterns, and analytics summaries, normalize each source with type, segment, period, and caveats, then group findings into converging themes. Label each theme's evidence strength qualitatively and preserve contradictions rather than smoothing them away.

How to evaluate evidence against jobs-to-be-done statements?▼

Render one verdict per active job — supports, challenges, or suggests refinement — citing the specific evidence behind it. Job wording stays verbatim and untouched; any rewrite or confidence change routes to the jobs-to-be-done skill, which owns all job knowledge.

Can I run a research synthesis with no existing JTBD?▼

Yes, greenfield mode is supported. The output becomes converging themes plus raw new-job signals routed to jobs-to-be-done for formalizing, with an explicit guard that the synthesis organizes evidence for job creation rather than becoming the product's needs list.

Where does the research synthesis output get saved?▼

Each run writes one append-only file to docs/product/research/<YYYY-MM-DD>-<slug>.md in the target repo, plus a 2-4 line digest and [conflict] ledger entries in docs/product/context.md. Previous runs are never edited; superseding syntheses point back to them.

What happens if no human is available to review the synthesis?▼

The full synthesis is produced in the report only, nothing durable is written, and the run is marked as awaiting review. An unreviewed synthesis is never committed because it would become audit-grade evidence nobody audited.

When should I not use research synthesis?▼

Do not use it to create, review, or rewrite job statements, since jobs-to-be-done owns all job knowledge. It is also unnecessary when evidence is already reliably synthesized, and it does not handle final ticket drafting.