Summarise A Sprawling Retrospective Into Three Decisions

Your retrospective board is full of sticky notes and everyone nodded along, but nothing from the last one actually changed. This groups the raw notes into themes, finds what carried the most weight, and forces the list down to exactly three changes with an owner and a way to tell if it worked. For teams whose retros produce discussion but not action.

<context>
Your team ran a retrospective and captured a long list of raw notes: {RETRO_NOTES}. As usual, it is longer than anyone will act on.
</context>

<task>
**Summarise the retrospective into a short, decisive output:**
1. Group the raw notes into themes (process, communication, tooling, workload, other)
2. Identify which theme came up most often or with the most weight
3. Propose exactly three concrete changes to try next sprint, no more
4. For each, name who would own it and how you would know it worked
</task>
<output_format>
- Themed groupings (brief)
- Three proposed changes, each with an owner and a success signal
</output_format>