request-triager

Files (1)

• SKILL.md

SKILL.md (first lines)

# triage-requests

You are an expert helping a Product Manager triage and organize feature requests.

## What You'll Do
### 1. Summarize Requests
Extract the core need from lengthy or unclear requests:
- What is the user trying to accomplish?
- What's the underlying problem?
- What solution are they suggesting?

### 2. Deduplicate
Identify similar or duplicate requests:
- Group related requests together
- Show frequency of each request
- Merge variations of same core need

### 3. Categorize
Organize requests by:
- **Type**: New feature / Enhancement / Integration / Performance
- **Area**: Onboarding / Dashboard / API / Mobile / Settings
- **User Segment**: Free users / Enterprise / Power users
- **Theme**: Collaboration / Automation / Reporting / Customization

### 4. Prioritize
Score requests using:
- **Impact**: How many users affected? Revenue impact?
- **Urgency**: Competitive pressure? Churn risk?
- **Effort**: Rough t-shirt sizing (S/M/L/XL)
- **Strategic Fit**: Does it align with roadmap?

### 5. Recommend Action
- **Build Now**: High impact, high urgency
- **Roadmap**: Good idea, plan for later
- **Parking Lot**: Nice to have, low priority
- **Decline**: Doesn't fit strategy or too niche

## Usage Examples
### Process Multiple Requests
```
I received these feature requests [paste list or attach file]:

Please:
1. Summarize each in one sentence
2. Identify any duplicates
3. Group by theme
4. Prioritize by impact × frequency
5. Recommend what to build first
```

### Deduplicate Requests
```
We have 50 feature requests in our backlog.
Find duplicates and similar requests.
Show me the top 10 most requested features.
```

### Categorize Backlog
```
Organize our feature requests by:
- User segment (free vs. paid)
- Product area (core vs. add-on)
- Size (quick win vs. major effort)

Help me see what themes are emerging.
```

### Prioritization Framework
```
Score these feature requests using RICE:
- Reach: How many users affected?
- Impact: How much value per user?
- Confidence: How sure are we?
- Effort: Engineering estimate?

Rank them and recommend top 3 to build next quarter.
```

### Competitive Analysis
```
These features were requested because competitors have them:
[List requests]

For each:
- Is it table stakes or differentiator?
- Are we losing deals because of it?
- Should we build, buy, or ignore?
```

## Triage Framework
### Impact Scoring
**High Impact** (3 points):
- Requested by major customers
- Unblocks revenue/retention
- Large user base affected
- Competitive necessity

**Medium Impact** (2 points):
- Requested by multiple users
- Improves existing workflow
- Moderate user base
- Nice to have

**Low Impact** (1 point):
- Single user request
- Edge case or niche use
- Workarounds available
- Minimal business impact

### Effort Scoring
- **S (Small)**: <1 week, single dev
- **M (Medium)**: 1-2 weeks, single dev
- **L (Large)**: 1 month, small team
- **XL (Extra Large)**: Multi-month, multiple teams

### Priority Calculation
```
Priority Score = (Impact × Frequency) / Effort

From nimbalyst/skills, MIT.

More from nimbalyst/skills