
Feature Eval
Score feature requests across strategy, demand, effort, and impact for defensible prioritization.
What You Can Do
This skill systematically evaluates feature requests against your product strategy using a structured matrix, eliminating subjective decision-making from your roadmap process. You'll score each request across four critical dimensions, generate defensible go/no-go recommendations backed by clear scoring rationale, and create accountability around prioritization decisions. The output surfaces real trade-offs between strategic fit, market demand, resource constraints, and business impact—giving you the justification you need to say 'no' to good ideas and align stakeholders on roadmap decisions.
Features
evaluates strategic alignment, customer demand, implementation effort, and business impact simultaneously
converts qualitative assessments into comparable scores for objective comparison across requests
produces clear recommendations with threshold-based logic and justification
explains the 'why' behind each decision for stakeholder communication
surfaces conflicts between effort, impact, and alignment to guide resource planning
process multiple feature requests in a single session with consistent scoring
validates requests against your product OKRs and positioning
weighs customer requests, market signals, and competitive gaps in scoring
Example Output
Request: "Add dark mode to mobile app"
Scoring Results:
- Strategic Alignment: 7/10 — Mentioned in Q2 OKRs but not primary focus
- Customer Demand: 8/10 — 340 feature requests, 23% of support tickets
- Implementation Effort: 4/10 — 2-3 weeks, existing design system supports it
- Business Impact: 6/10 — Improves engagement, unclear revenue impact
Overall Score: 6.25/10 | Recommendation: QUEUE FOR Q3 (High demand + manageable effort, but lower strategic priority)
Rationale: Dark mode has strong customer demand and reasonable effort, making it a good candidate when strategic priorities allow. Pair with other mobile improvements for higher impact.
Request: "Build API for third-party integrations"
Scoring Results:
- Strategic Alignment: 9/10 — Core to platform expansion strategy
- Customer Demand: 7/10 — Top 5 enterprise customer requests
- Implementation Effort: 8/10 — 8-10 weeks, requires security review
- Business Impact: 9/10 — Unlocks new revenue stream, reduces churn
Overall Score: 8.25/10 | Recommendation: PRIORITIZE FOR Q2 (High impact and strategic fit justifies resource investment)
Rationale: Despite significant effort, the strategic alignment and business impact justify the investment. Recommend allocating dedicated engineering capacity.
What's Included
- SKILL.md: Complete evaluation framework with scoring methodology
- Feature Evaluation Matrix Template: Structured spreadsheet for capturing and scoring requests
- Scoring Rubric Checklist: Detailed guidance for assessing each of the four dimensions
- Linear Integration Workflow: Step-by-step setup for syncing feature requests from Linear into evaluation
- Go/No-Go Decision Framework: Threshold logic and stakeholder communication templates for recommendations
Who It's For
- Product Managers & Group Product Managers — Managing feature backlogs and making prioritization decisions
- Head of Product / Chief Product Officers — Aligning executive stakeholder expectations on roadmap trade-offs
- Product Operations Managers — Standardizing evaluation processes across product teams
- Startup & Scaleup Founders — Defensibly saying 'no' to feature requests when resources are constrained
- Enterprise Product Leads — Managing requests from multiple customer segments and internal stakeholders
Best For
- Backlog grooming sessions — Quarterly or bi-weekly evaluation of 20+ accumulated feature requests
- Executive requests & disputes — Objective justification when stakeholders disagree on priorities
- Customer-driven features — Weighing competitive requests against strategic direction
- Resource constraint decisions — Clear trade-off analysis when you can't build everything
- Roadmap planning — Building defensible quarterly or annual product plans with stakeholder buy-in







