feature-prioritization
Feature Prioritization
Decide what to build next based on impact, not excitement.
How to use
/feature-prioritizationApply 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"
Decision Rules
- If a feature serves <10% of users, it probably doesn't belong in v1
More from dragoon0x/product-skills
prd-writing
Write product requirement documents that engineers want to read and can actually build from. Covers structure, scope discipline, and the balance between clarity and over-specification. Use when writing PRDs, reviewing spec quality, or when engineering keeps asking clarifying questions.
1freemium-vs-paid-gate
Decide whether a product should offer a free tier, free trial, or go straight to paid. Structured decision framework based on economics, distribution model, and competitive landscape. Use when launching a new product or reconsidering your pricing model.
1error-recovery
When things break, guide people forward instead of leaving them stranded. Error message copy, retry patterns, graceful degradation, and recovery flows. Use when building error handling or failed state UIs.
1cta-patterns
Design calls-to-action that people actually click. Covers button copy, placement logic, urgency without manipulation, and progressive commitment. Use when reviewing pages for conversion potential or when CTA copy feels generic.
1onboarding-flow
Design first-run experiences that create the aha moment fast. Reduces time-to-value by sequencing actions, progressive disclosure, and contextual guidance. Use when building signup flows, product tours, or empty states.
1user-psychology
Apply motivation, friction, and trust patterns to product decisions. Maps cognitive biases and behavioral triggers to specific UI and copy choices. Use when reviewing flows for drop-off points or when something feels right but doesn't convert.
1