Feature triage

Feature triage

Sort a batch of feature requests into what's worth a spec, what's worth a quick fix, and what to decline.

Workflow

1. Gather the requests

Based on $ARGUMENTS (default: all):

• Slack: search the product-feedback or feature-request channels for messages tagged/flagged as requests in the last 14 days.
• Notion: pull any pages in the intake database that are unresolved.
• Gmail: if "recent-emails", search for customer emails matching request-like patterns ("can you add", "would be great if", "feature request") in the last 30 days.

Report counts per source before scoring.

2. Score each request

For each request, assign:

Dimension	Scale	What it means
Reach	1–5	How many users are affected. 1 = one customer, 5 = most of the active base.
Impact	1–5	How much it moves the needle for affected users. 1 = mild convenience, 5 = unblocks core workflow.
Effort	1–5	Eng cost. 1 = a day, 5 = multi-quarter. Flip for the score (lower effort = higher score).
Strategic fit	1–5	Alignment with current roadmap theme. 1 = off-thesis, 5 = core to the quarter.

Final score: Reach × Impact × Strategic_fit / Effort. Round to 1 decimal.

Don't pretend precision you don't have. If you genuinely can't score a dimension, write ? and explain what you'd need to know.

3. Recommend

For each request, pick one:

• Spec it — worth a PRD. Score ≥ 10 typically.
• Quick win — small, high-value, no spec needed. Usually low effort + high reach.
• Watch — one-off but worth tracking. Log it, don't act.
• Decline — politely close the loop with requester. Below the bar for this quarter.

4. Output

# Feature triage — <date>

Pulled N requests. Top 10 by score:

| # | Request | R | I | E | Fit | Score | Recommend | Source |
| --- | --- | --- | --- | --- | --- | --- | --- | --- |
| 1 | <one-line> | 4 | 5 | 2 | 4 | 40 | **Spec it** | <link> |
| ... |

## Recommended this cycle
- **Spec it:** <request>, <request>
- **Quick wins:** <request>
- **Decline:** <request> — drafted reply below

## Drafted replies for declines
<For each decline, a 2-3 line polite reply the user can send on Slack/email. Don't send.>

Don't

• Don't bundle multiple distinct requests into one row — splits hide signal.
• Don't score based on who asked. Score on the merit.
• Don't send decline replies. Draft them for the user to send.