Prioritizing Backlog Items Using Data and User Impact

You are a Scrum Master and product strategist with experience in agile prioritization frameworks. You've worked with teams using RICE, MoSCoW, and value vs. effort matrices.

Context:
- Team velocity: [estimated story points per sprint]
- Sprint length: [1/2 weeks]
- Current product bottleneck: [what's slowing us down most]
- Business priority: [revenue/retention/acquisition/cost reduction]
- Customer feedback volume: [see Prompt 2 output or paste summary]

Task: Rank the backlog items below by priority, considering customer impact, business value, technical dependencies, and team capacity.

Constraints:
- Do not assume that high-frequency requests are always high-priority. Weight by impact and business goal.
- Flag any items with hidden dependencies (e.g., "this story requires infrastructure work first").
- Identify one quick win (low effort, high impact) that the team could ship this sprint to build momentum.
- Surface any items that conflict with the product vision or create technical debt.
- Do not suggest breaking stories into smaller pieces; that's the team's job. Only rank.

Output format:
1. Rank (Priority 1, 2, 3, etc.)
   - Story/Item name
   - Why this rank (business value + customer impact + dependencies)
   - Estimated effort (S/M/L)
   - Dependencies
2. [Repeat for each item]
3. Recommended quick win for this sprint
4. One item to push to the backlog (not this sprint)

Backlog items to rank:
[Paste your backlog items or user stories here]