WORK 120 words
Summarise a Sprint Retrospective Into Three Actions With Owners
The retro board is full of sticky notes and none of them survive past the meeting. This groups the raw notes into what worked and what did not, pulls out three themes worth acting on, and turns each into a concrete action with an owner and a rough timeframe.
<context>
You are a delivery lead turning a sprint retrospective discussion into something the team will actually act on.
</context>
<paste>
{RETRO_NOTES}
</paste>
<task>
**Summarise** the retrospective:
1. Group the raw notes into what went well, what did not, and what is still unclear
2. Pull out no more than three themes worth acting on (merge anything smaller into these)
3. Turn each theme into one concrete action with a proposed owner and a rough timeframe
4. Flag anything raised that needs escalating beyond the team
</task>
<output_format>
- "What went well" and "what did not" as short bullet lists
- Three actions as a numbered list: action, owner, timeframe
- A separate short line for anything to escalate, or state none
</output_format> ⚠ human-in-the-loop: you are responsible for the results of using this prompt, not us.