Set up
Try a plugin
The Product Management plugin ships with /synthesize-research and other discovery skills as a starting point, already structured to cluster raw signal into themes and rank them. If your admin manages plugins and it's not available yet, skip this step. The prompt below works without it.
/synthesize-researchSynthesize user research from interviews, surveys, and feedback into structured insights./roadmap-updateUpdate, create, or reprioritize your product roadmap.Connect your tools
Claude is more powerful when it works directly with your systems. You control permissions and access. Learn about tool access(opens in new tab).
Add a connector(opens in new tab) for each tool you want Claude to use.
Set your working folder
Drag the files you'll use (the NPS verbatim export, the support ticket CSV, the sales call snippets, the six interview transcripts) into one folder on your machine, then point Claude at it. Claude reads from it and writes the Voice of Customer brief back to it. If you run this every quarter, create a project(opens in new tab) from that folder so your sources, instructions, and memory stay attached.
The prompt
Copy this into Claude
Read this folder plus the #product-feedback Slack channel and the open Zendesk tickets tagged feedback. Cluster everything into 5 to 7 themes, count how often each shows up and how severe it is, pull the best verbatim for each, flag which map to a Linear roadmap item versus net-new, and write a one-page Voice of Customer brief for roadmap review.
Why this works
Give a number range. "5 to 7 themes" forces real clustering instead of a forty-row tag list, so the brief fits on one page and the roadmap conversation stays on the top signals.
Ask for frequency and severity. Naming both gives Claude your ranking criteria, so the themes come back ordered by what matters to planning rather than just by how often they came up.
Ask for the single best example. The single best quote does more in roadmap review than a wall of evidence; Claude picks the strongest line and links the rest underneath.
Compare against your existing plan. "Map to a Linear roadmap item versus net-new" means the brief arrives already split into validate-what-we-planned and here-is-what-we-missed.
Get a better draft
Add an example to match. Drop an example you like into the folder and Claude matches your structure and voice.
Ask it to flag uncertainty. Add "flag anything you're not confident about" so you know where to look first when you review the draft.
Make Claude work for you
A plugin skill is a starting point. Customize it with your own practices and expertise, or save what you've done as a skill of your own. A few minutes of conversation and it runs with your standards from then on.
Make what we've done in this task so far into a skill, or edit the /synthesize-research skill with my feedback.
Make it repeatable
Run it ahead of every roadmap review
Feedback piles up between planning cycles whether or not anyone is reading it. Ask Claude to set up a scheduled task, or open Scheduled in the sidebar, and the customized skill produces a fresh brief the Friday before each roadmap review.
Set up a scheduled task for every Friday at 4pm: run /synthesize-research against Product/voc-<current-quarter> plus the live Slack and Zendesk sources, and write the brief to that folder as voc-brief-<date>.md.
Runs /synthesize-research against the quarter's VoC folder plus live Slack and Zendesk and writes the one-page brief back to the folder.
Share with your teammates
Your customized /synthesize-research now carries your severity scale, your standing sources, and your brief format. Share it so every PM on the team clusters feedback the same way, and roadmap review reads one consistent VoC page no matter whose area it covers.