prioritize

# Prioritize: Feature Ranking and Scoring Score and rank features, initiatives, or backlog items using established PM frameworks. Auto-detects the right framework and mode from context. ## When to Activate - User says "prioritize", "rank these", "what should we build next?" - User asks for RICE, ICE, WSJF, or any scoring framework - User needs to make scope cuts or trade-off decisions - User has a list of features and needs to decide order ## Modes Auto-detect from user phrasing. If ambiguous, ask. | Mode | When | Output | |------|------|--------| | **Stack rank** | "What should we build next?" | Ordered list with reasoning | | **Scoring** | "Score these 10 features" | Framework table with scores | | **Opportunity assessment** | "Where's the biggest opportunity?" | Gap analysis, underserved areas | | **Trade-off analysis** | "Should we do A or B?" | Side-by-side comparison | | **Scope cut** | "We need to cut scope" | Keep/cut/defer recommendations | ### Detection heuristics - "rank", "order", "what first", "what next" → Stack rank - "score", "RICE", "ICE", "rate these" → Scoring - "opportunity", "gap", "underserved" → Opportunity assessment - "A or B", "trade-off", "which one", "compare" → Trade-off analysis - "cut scope", "too much", "reduce", "what can we drop" → Scope cut ## Frameworks ### RICE (default for scoring mode) Best for: Large backlogs, cross-team prioritization, when you need a defensible number. | Feature | Reach | Impact | Confidence | Effort | RICE ...