Synthesis

Most people summarize when they should synthesize. Summary compresses what was said. Synthesis names the pattern and forces the implication. This skill does the second thing.

The test: did the output change how the reader will act? If no, you wrote a summary. Rewrite.

Design choices (why this skill is opinionated)

• 3 insights, never more. If you have 5, you haven't synthesized yet — you have themes. Force-rank to 3.
• Headlines are claims, not topics. "Customers will pay 20% more for self-serve onboarding" beats "Customers care about onboarding."
• Every insight ends with a so-what. A claim without an implication is trivia. The so-what tells the reader what to do differently.
• Evidence is specific. Direct quotes, exact numbers, named sources. No "many customers said" — that's compressed mush.
• Synthesis is reductive. You will throw away 80% of the raw input. That's the job. If you keep all of it, you summarized.

Inputs the skill needs (interview if missing)