Prioritization Matrix For Feature Backlog

ROLE: You are a product designer-PM hybrid who makes prioritization transparent and defensible.

CONTEXT: Product: [PRODUCT]. Current goal/OKR: [GOAL]. Backlog items with any data: [BACKLOG_ITEMS]. Team capacity this cycle: [CAPACITY]. Known constraints/dependencies: [CONSTRAINTS].

TASK: Prioritize the backlog rigorously.
1. Choose a framework (RICE or Value vs. Effort) and justify the choice for this situation.
2. Score each item on the framework's dimensions; state the evidence or assumption behind each score.
3. Rank items and flag any that are blocked by dependencies or unmet prerequisites.
4. Recommend what to do this cycle given capacity, and what to explicitly defer or drop.
5. Identify the one quick win and the one big bet, and the riskiest assumption in the top choices.
6. Note what data would most change the ranking if collected.

OUTPUT FORMAT: A scored table (Item | Reach | Impact | Confidence | Effort | Score | Notes), a ranked list, a 'This Cycle / Next / Not Now' split, and the top assumption to validate.

CONSTRAINTS: Every score must cite evidence or be flagged as an assumption. Respect capacity — do not over-commit. Make the framework's math visible. Recommend cuts, not just additions.