Engineering
feature-prioritization avatar

feature-prioritization

A structured decision-making tool that applies RICE, MoSCoW, Kano, and value-effort frameworks to prioritize software features, roadmap items, and build-vs-defer decisions with data-driven objectivity.

Introduction

The feature-prioritization skill is a specialized product strategist agent designed to eliminate subjective debates and cognitive biases in software development. By leveraging proven industry-standard frameworks, it transforms abstract feature requests into quantifiable, defensible, and ranked priority lists. This tool is essential for product managers, technical leads, and engineering teams operating under tight resource constraints who need to justify their roadmap choices to stakeholders.

  • Multi-Framework Support: Expert implementation of RICE (Reach, Impact, Confidence, Effort), MoSCoW, Kano model, Value vs. Effort, Cost of Delay, and custom Weighted Scoring.

  • Data-Driven Synthesis: Bridges the gap between qualitative user insights and quantitative business metrics to suggest the highest ROI initiatives.

  • Transparency & Accountability: Maintains rigorous audit trails of decision-making, including explicit assumptions, confidence levels, and trade-off considerations.

  • Anti-Bias Enforcement: Actively suppresses anti-patterns such as HiPPO (highest-paid person's opinion), recency bias, and the 'squeaky wheel' phenomenon by forcing reliance on objective scoring.

  • Cross-Validation Protocols: Enforces high-stakes decision validation by requiring multiple frameworks when data is ambiguous or high-risk.

  • Inputs/Outputs: Accepts raw feature lists, user metrics, and business requirements; outputs a structured PriorityDecision JSON object containing ranked items, rationale, trade-offs, and future review dates.

  • Operational Best Practices: Always distinguish between measured data and estimates; use 50% confidence flags for speculative items; ensure scoring formulas are transparently shared with stakeholders.

  • Strategic Application: Use during sprint planning, quarterly roadmap reviews, build-vs-defer dilemmas, or when resolving conflicting technical debt vs. feature delivery priorities.

  • Constraints: Does not fabricate data. It requires specific context for effective calculation and encourages iterative refinement of estimates as project data matures.

Repository Stats

Stars
265
Forks
39
Open Issues
0
Language
Shell
Default Branch
main
Sync Status
Idle
Last Synced
Apr 29, 2026, 06:06 AM
View on GitHub