Distinguish between customer solutions and underlying problems using structured evaluation frameworks.Documentation Index
Fetch the complete documentation index at: https://docs.getcore.me/llms.txt
Use this file to discover all available pages before exploring further.
Tools Required
This skill runs using CORE memory only. No integrations required.Step 1: Clarify Your Goal
Confirm the product objective and desired outcomes that will anchor your prioritization decisions. Document what success looks like for your product over the next quarter.“What are your top 2-3 product goals this quarter? How will you measure success?”
Step 2: Group Requests by Theme
Organize all feature requests into logical categories and identify common patterns. Look for multiple requests addressing the same core problem—these patterns signal real customer needs. Ask: “What are the recurring themes or problems appearing in multiple requests?”Step 3: Evaluate Strategic Fit
Assess how each theme aligns with your stated product goals. Reject requests that don’t support your strategic direction, regardless of volume.Step 4: Rank Top 3 Features
Score each theme across these dimensions:- Impact: Customer value delivered and user reach affected
- Effort: Resource requirements and implementation complexity
- Risk: Technical uncertainty and market validation gaps
- Strategic alignment: Connection to stated product goals
Step 5: Deep Dive on Winners
For each top-ranked feature, document:- Supporting customer rationale and underlying problems being solved
- Alternative approaches or solutions worth exploring
- Key assumptions carrying the most risk
- Low-effort validation methods to test assumptions
Output Format
Feature Request Analysis 📊 Grouped Themes
| Theme | Request Count | Strategic Fit | Key Insight |
|---|---|---|---|
| [Theme Name] | [#] | High/Medium/Low | [Pattern or customer need] |
- Impact: [Expected customer value and reach]
- Effort: [Resource requirements - Small/Medium/Large]
- Risk: [Technical and market risks]
- Strategic Fit: [How it supports goals]
- Validation Method: [Low-effort test to validate]
Edge Cases
- Volume bias: High request volume doesn’t equal market demand. Synthesize underlying problems rather than counting votes.
- Solution requests: Customers often propose solutions instead of articulating problems. Ask why they want the feature to uncover real needs.
- Niche requests: A few passionate customers requesting highly specific features shouldn’t override broad market signals.
- Competitor copycat: Request for feature competitor has doesn’t automatically mean it’s valuable for your product.
- Technical feasibility unknown: If you can’t assess effort, allocate spike time before full prioritization.