Who this is for
Scrum masters and dev teams who want retros that actually change the next sprint, not the same complaints on repeat.
The moment this saves you
Every retro we surface the same problems, agree to fix them, and then nobody writes down who owns what, so next sprint we have the exact same retro all over again.
See it work
Messy spoken thought in. A clean, structured artifact out.
Okay retro for this sprint. What went well, the new PR review rotation really helped, reviews got faster and people felt less bottlenecked. Deployment was smooth this time too. What didn't go well, we massively underestimated the migration ticket, it ate three days more than planned and blocked two other things. Also standups have been running long, like 25 minutes. Actions, Sam's going to timebox standups to 10 minutes starting Monday, and we agreed to add a buffer for any ticket touching the database. I'll set up the estimation thing.
Sprint retro, June 5, 2026
What went well
- New PR review rotation: faster reviews, fewer bottlenecks
- Smooth deployment
What didn't go well
- Migration ticket badly underestimated, ran 3 days over, blocked two other tickets
- Standups running long (~25 min)
Action items
- ☐ Timebox standups to 10 minutes from Monday, Sam
- ☐ Add a buffer for any ticket touching the database, team
- ☐ Set up the estimation process, Me
The workflow
Record a voice note
Hit the hotkey and talk, no formatting, no typing.
Tag it with this context
Contextli shapes your words into the structured output above.
Find it later
Everything's searchable and organised by context.
Pull it into Claude or ChatGPT
Bring your contexts straight into your AI tools with the Contextli MCP.
Your raw recording and transcription stay on your device, so you can always go back to the original.
The prompt behind this context
I'm going to talk through a sprint retrospective. Turn it into structured retro notes: a bold "Sprint retro, [today's date]" heading, then three bold sections: **What went well**, **What didn't go well**, and **Action items** (a checkbox list, each with an owner I named as `*owner*`, using `*Me*` for mine and `*team*` for shared). Keep specifics, ticket names, and numbers. If an agreement has no clear owner, still list it and mark `*owner: TBD*`. Don't invent items or owners. Output only the notes.
Make it your own. This is a starting point. Once it's in Contextli, tweak the instructions so the output comes out exactly how you like it.
Use this context
One click copies it and shows you exactly how to drop it into Contextli.
Next, open Contextli, go to the Contexts page, click Import, choose From JSON, paste, then Import Context. It is ready to use.
Make it your own. This is a starting point. Once it's in Contextli, tweak the instructions so the output comes out exactly how you like it.
Your raw recording and transcription stay on your device, so you can always go back to the original.
Related contexts
Standup Update
Standup's in two minutes and you're still reconstructing yesterday. Skip the typing. Talk through your day in whatever order it comes out, and get a clean yesterday, today, and blockers post you can drop straight in the thread.
On-Call Incident Note
You just fought a fire at 2am and the postmortem is tomorrow, when half the timeline will be gone. Talk through what broke, what you did, and what fixed it, right now. You get a postmortem-ready note while the details are still sharp and real.
1-on-1 Note
Your 1:1s blur together and you walk into the next one having forgotten what you promised in the last. Recap it the moment you leave, what they raised, what you committed to, and never again say 'remind me what we talked about last time.'
Questions people ask
Questions scrum masters ask about Sprint Retro Notes
What should a structured note include?
A good structured note includes a clear title, steps to reproduce the issue, the expected behavior, the actual behavior observed, the severity or priority, and the environment details such as OS, browser, and app version. The Sprint Retro Notes context structures your spoken description into these fields automatically, so nothing gets left out when you are in the middle of debugging.
How do I write a structured note in under a minute?
Speak what you found: describe the issue, what you expected, what actually happened, and how bad it is. The Sprint Retro Notes context structures your words into a complete structured note you can paste directly into Jira, Linear, or GitHub Issues. Most take under 60 seconds to dictate, so you capture them without breaking your flow.
How do developers capture issues without interrupting their flow?
The key is to capture the issue immediately without switching context mentally. Contextli lets you speak a quick voice note describing it and produces a structured note from it. You can dictate while the issue is still on screen, then paste the formatted output into Jira, Linear, or GitHub Issues when you come up for air. No typing is required during the capture step.
Can I write a structured note by talking instead of typing?
Yes. The Sprint Retro Notes context lets you speak a description in plain language and converts it into a structured structured note with all the required fields filled. You speak the way you would explain it to a colleague, and the context handles the formatting.
How do I add this context to Contextli?
Copy the context on this page, then open Contextli and go to the Contexts page. Click Import, choose From JSON, paste it into the Import from Clipboard window, and click Import Context. It is ready to use in under 30 seconds. If you do not have Contextli yet, you can download it for free first.
Is my voice recording private? Does Contextli send it anywhere?
Your voice recording and the transcription are stored on your device only. Contextli processes your audio locally and does not send your recordings or transcription text to any server. The structured output it produces is text you control, and you decide where it goes.
Can I change what the output looks like?
Yes. Every context in Contextli is a starting point you can edit. Open the context in the app, change the instructions to adjust the structure, tone, or fields, and save. The next time you use it, the output reflects your changes. You are not locked into the default format.
Do I need to install an app to use this context?
Yes. Contextli is a free app. Download it, then copy this context and paste it into the Import from Clipboard window on the Contexts page. The whole process takes about 30 seconds.