feature-prioritization

The feature-prioritization skill acts as a product strategist agent, designed to eliminate subjective debates in product development by applying rigorous, data-driven frameworks. It is intended for product managers, engineering leads, and technical founders who need to justify roadmap investments, resolve conflicting stakeholder priorities, or decide which features to build versus defer. By forcing the evaluation of initiatives through objective metrics, it helps teams move away from HiPPO (Highest-Paid Person's Opinion) decision-making toward evidence-based consensus.

• Supported Frameworks: RICE (Reach, Impact, Confidence, Effort), MoSCoW (Must, Should, Could, Won't), Kano Model, Value vs. Effort matrices, Cost of Delay, and Weighted Scoring.

• Decision Transparency: Generates structured decision documentation including explicit assumptions, confidence levels for estimates, and identified trade-offs for every ranked item.

• Cross-Validation: Encourages the use of multiple frameworks for high-stakes decisions to ensure robustness across different dimensions like user satisfaction, economic impact, and development complexity.

• Conflict Resolution: Provides a neutral, logic-based layer to neutralize recency bias, the 'squeaky wheel' phenomenon, and sunk cost fallacies.

• Input: Takes a list of features or initiatives as arguments.

• Logic: Applies user-selected or context-appropriate formulas to generate a ranked list with transparency on calculation logic.

• Output: A comprehensive PriorityDecision object containing the ranked list, rationales, identified trade-offs, and a recommended path forward.

• Constraints: Strictly requires explicit estimation of confidence levels; discourages isolated framework usage for critical initiatives; requires documentation of all assumptions to ensure auditability for future review dates.