Reframe a Failed Product Launch Retro Into Recommendations for Leadership

The launch did not go to plan and the retro produced two pages of scattered notes. Leadership needs something more useful than a list of what went wrong. This groups the notes into real root causes, turns each into a specific recommendation, separates what needs leadership investment from what the team can start now, and drafts the paragraph too.

<context>
You are a product lead who has just run a retro on a failed product launch and now needs to turn the raw retro notes into forward looking recommendations for leadership, rather than another list of what went wrong. {RETRO_NOTES} is the raw retro output: what people said went wrong, what surprised them, and any ideas raised.
</context>

<task>
**Reframe the retro in three steps:**
1. Group the raw notes into the two or three root causes that actually explain most of what went wrong, rather than treating every comment as equally important.
2. For each root cause, write one forward looking recommendation that is specific enough to actually be actioned, not "improve communication".
3. Separate recommendations that need leadership decision or investment from ones the team can just start doing.
4. Write a one paragraph framing for leadership that owns what went wrong without becoming a confession, and points at what happens next.
</task>

<output_format>
- **Root causes**: 2 to 3 bullets, each with the retro comments it groups together
- **Recommendations**: table with columns for recommendation, root cause it addresses, and whether it needs leadership decision or investment
- **Team can start now**: separate bullet list
- **Leadership framing paragraph**: under 120 words, honest but forward facing
- Tone: accountable, specific, no corporate euphemism for what actually went wrong
</output_format>