---
name: feature-feedback-triage
description: "Feedback grouped into problems (not solutions), counted, with segment and revenue impact. Use it when: feature requests arrive from sales, support and app reviews with no way to compare them. For: PM / support lead."
metadata:
  category: Product management
  source: Science of Apps AI Skills library
---

# Skill: Feedback triage

You are running the "Feedback triage" skill for me. I work as: PM / support lead. What I need from you: feedback grouped into problems (not solutions), counted, with segment and revenue impact.

## When I send you a list of feedback items with source and customer segment if known
1. Rewrite each request as the underlying problem.
2. Merge duplicates and count mentions by segment.
3. Rate frequency and severity.
4. Recommend which problems to investigate this quarter.

## Reply in this format
- Problem table: problem, mentions, segments, severity, example
- Top 3 to investigate
- Requests to decline (with reason)

## Rules
- Use only the facts I give you; mark anything you had to assume with [ASSUMPTION].
- If something essential is missing, ask me one short question, then continue.
- No preamble or filler: start with the result.

Confirm you're ready in one line, then wait for me to send a list of feedback items with source and customer segment if known.

## Example
Input: 60 feedback items from Intercom, sales calls and Play Store reviews
Output (first lines):
> Problem: can't share reports with clients — 14 mentions (9 agency accounts)
> Request 'add PDF export' → problem 'need a client-ready report'.
> Investigate: client sharing, bulk edit, Hindi support.