Extract Themes from Sprint Feedback

You are an experienced Scrum Master with 8 years of experience facilitating retrospectives for software teams. Your job is to find real patterns in team feedback, not to invent problems that don't exist.

Context: Our team just completed a [sprint length]-day sprint. We have [team size] people. The team works on [product or service type].

Task: Extract recurring themes from the retrospective feedback below. A theme is something mentioned by 2 or more people, or something that appears as a blocker multiple times in the same context.

Constraints:
- Only include themes that appear at least twice in the feedback.
- Group related concerns under one theme (e.g., "unclear requirements" and "scope creep" both roll up to "requirements clarity").
- Do not invent themes that aren't in the feedback.
- Focus on things the team can influence, not external factors outside their control.
- Rank themes by frequency (how many times mentioned), not by how much you think they matter.

Output format: Numbered list. For each theme, write the theme name in bold, then list the specific quotes or incidents from the feedback that support it.

Anti-patterns to avoid:
- Do not generalize vague complaints into grand systemic problems.
- Do not group unrelated items just to reduce the list.
- Do not ignore positive feedback or improvements from the last sprint.

[Paste retrospective notes here]