Prioritize Features

What Is This?

Overview

Prioritize Features is a structured skill designed to evaluate and rank a backlog of feature ideas based on four core dimensions: impact, effort, risk, and strategic alignment. Rather than relying on gut instinct or the loudest voice in the room, this skill applies a consistent analytical framework to surface the top five features worth pursuing at any given time. It transforms an unstructured list of ideas into a ranked, defensible set of recommendations.

The skill works by accepting a backlog as input, whether that is a plain text list, a spreadsheet, or a structured document, and then scoring each item across the four evaluation dimensions. The output is a prioritized shortlist with clear reasoning behind each recommendation. This makes it easier for product teams to communicate decisions to stakeholders and align development resources with business goals.

Product decisions made without a structured process often lead to wasted engineering time, missed market opportunities, and scope creep. This skill provides a repeatable, transparent method for making those decisions with confidence and consistency.

Who Should Use This

• Product managers who need to present a prioritized roadmap to leadership or engineering teams
• Engineering leads who want to align sprint planning with business value rather than arbitrary request order
• Startup founders evaluating which features to build first with limited resources
• UX designers advocating for user-facing improvements against competing technical requests
• Project managers responsible for scope decisions on fixed-timeline deliverables
• Business analysts translating stakeholder requests into a ranked development queue

Why Use It?

Problems It Solves

• Backlogs grow faster than teams can process them, leaving valuable ideas buried and forgotten without a clear ranking system
• Stakeholder pressure often pushes low-value features to the top of the queue, displacing work that would deliver greater business impact
• Teams frequently underestimate effort or ignore risk when making scope decisions, leading to delays and rework
• Without strategic alignment checks, individual features may be technically sound but disconnected from company goals
• Prioritization discussions become subjective and time-consuming when there is no shared scoring framework to anchor the conversation

Core Highlights

• Scores features across impact, effort, risk, and strategic alignment in a single pass
• Produces a ranked top-five list with written justification for each recommendation
• Accepts multiple input formats including plain text lists, CSV files, and structured backlogs
• Applies consistent criteria across all items, removing bias from the evaluation process
• Surfaces trade-offs explicitly so teams can make informed decisions rather than assumptions
• Integrates with existing product management workflows without requiring new tooling
• Generates output that can be shared directly with stakeholders or imported into planning tools

How to Use It?

Basic Usage

Invoke the skill by passing your backlog as the argument. A minimal example using a plain text list looks like this:

prioritize-features "Add dark mode, Improve search speed, Build API v2, Add SSO login, Redesign onboarding, Export to CSV, Add webhook support"

The skill will evaluate each item and return a ranked list of the top five with scores and reasoning.

Specific Scenarios

Scenario 1: Quarterly planning cycle. A product manager exports the current backlog from Jira as a CSV file and passes it to the skill before the planning meeting. The output gives the team a starting point for discussion rather than a blank slate.

Scenario 2: Scope reduction under deadline pressure. An engineering lead has ten features in the current sprint but capacity for only six. The skill evaluates all ten and identifies which four to defer based on effort and risk scores.

Real-World Examples

A SaaS company uses the skill to evaluate fifteen feature requests submitted during a customer advisory board meeting. The output identifies that SSO login and bulk export rank highest due to high impact and low risk, while a custom reporting module scores low due to high effort and unclear strategic fit.

A mobile app team runs the skill against their backlog before each two-week sprint, using the output to populate their sprint board with confidence that the selected items align with the current product strategy.

Important Notes

Requirements

• A backlog of at least three feature ideas is needed to produce a meaningful ranked output
• Features should be described with enough detail for the skill to infer scope and user value
• Strategic context such as target audience, current business stage, or active OKRs improves output quality