---
name: "feature-request-triage"
description: "Sort feature requests by the problem behind them, who asked, how often, and what is missing."
triggers: ["feature requests", "triage requests", "request backlog", "customer asks", "duplicate requests"]
version: "1"
---
# Feature request triage
Use this for a backlog of requests from customers, sales, or the team.
## Find the problem behind the ask
For each request note who asked, their plan and segment, the date, and the
exact words. Ask what they were trying to do when they wanted it, what they
do today instead, and how often. If the request does not say, mark the
problem unknown rather than guessing it.
## Merge and count
Merge requests that share a problem even when they ask for different
solutions. For each merged item give:
- the problem in one sentence;
- number of requests and distinct accounts;
- segments and plans, and any revenue the team has supplied;
- the solutions users proposed;
- what is still missing to judge it.
## Triage list
Sort items into **look closer**, **already planned**, **needs evidence**, and
**not now**, with a reason for each. Name who should follow up with which
customer and what to ask.
Do not reply to customers, promise a feature, or change the tracker yourself;
recommend and draft. Never invent a requester, a count, or a revenue figure.