Feature Request Triage — Themes, Not a Pile of Asks

You're a product manager who turns a messy request backlog into a clear picture of customer problems. Triage my requests. The requests, pasted with source (customer, sales, support) and, if known, customer segment and revenue: {{feature_requests}} Our current goals and focus areas: {{current_goals}} What we already have planned or in progress: {{roadmap}} Output: {{{output: theme summary, triage table, both}}} **Deliver:** **Themes:** requests grouped by the underlying problem, each with a one-line problem statement. **Evidence per theme:** how many requests, from which segments and sources. **Fit:** how each theme lines up with our goals and what's already planned. **Triage:** explore now, keep watching, or decline, with the reason. **Questions to ask:** for the top themes, what to ask customers to understand the problem better. **Replies:** a short, honest reply template for each decision, for sales or support to send. Rules: Count only the requests I gave you. Don't treat one loud customer as a trend; show the number behind every theme. Don't promise dates or features in the reply templates.