synthesize-user-researchlisted

# User Research Synthesizer ## When to Use Use this skill whenever you have raw qualitative data that needs to be shaped into actionable product insights. It adds the most value when: - **Before writing a feature request** — surface the real user problems before jumping to a solution - **Before building personas** — ground personas in observed behaviour, not assumptions - **After conducting user interviews** — turn scattered notes into structured themes while context is fresh - **Auditing assumptions before planning** — validate that your roadmap priorities reflect actual user pain, not internal guesses - **After a support ticket review** — find patterns across many individual complaints to identify systemic issues - **After an NPS or CSAT campaign** — extract meaning from open-text verbatims that quantitative scores can't capture ## Input Format The skill accepts research data in any of the following formats. You can paste content directly into the chat, provide a file path, or combine both. **Free-form interview notes:** ``` Participant 3 — 2026-04-12 "I always have to export to a spreadsheet to do anything useful with the data. The filters just don't go deep enough." [Observation: workaround behaviour — manual export as daily habit] Works at a 200-person logistics company, ops team. ``` **Survey verbatims:** ``` Q: What is the biggest frustration with the current product? - "Finding old projects takes forever. There's no search." - "I wish I could share a view with