Feature Prioritization

Decide what to build next based on impact, not excitement.

How to use

• /feature-prioritization Apply prioritization constraints to feature decisions in this conversation.
• /feature-prioritization <features> Score and rank a set of features.

Constraints

Scoring Framework

• MUST evaluate each feature against: reach (how many users), impact (how much it changes behavior), confidence (how sure are we), effort (how long to build)
• MUST produce a ranked list, not a tier system. Force hard choices.
• NEVER give two features the same priority. If they feel equal, dig deeper.
• SHOULD separate "must-have for launch" from "nice to have" from "later"