PromptWork
Build a retrospective agenda from sprint events
Turn a list of what happened during a sprint into a retrospective agenda: themes to probe, blame-free questions and a concrete decision format.
Last updated
Fill in the blanks
Assembled in your browser — nothing you type is stored or sent anywhere.
Your prompt
Build a retrospective agenda for the checkout squad covering Sprint 24 (Aug 18-29), based on the events below.
Group the events into 2-4 themes worth discussing (not a topic per event). For each theme, write one open question that invites explanation rather than assigning blame (ask about the process or circumstances, not "why did X person do Y"). End the agenda with a decision format for turning discussion into action: a fixed number of concrete changes the team will commit to trying next sprint, each with an owner. If an event in the list is too vague to turn into a real discussion theme, leave it out rather than forcing a theme around it.
Sprint events:
the payment gateway change took 3 days longer than estimated because of an undocumented rate limit we hit in testing. one PR sat unreviewed for 4 days because the usual reviewer was out and nobody picked it up. the demo went well, stakeholders liked the new refund flow. two people said standup is running long and feels repetitive.
Model-agnostic — works in Claude, ChatGPT, Gemini or any AI chat.
Why this prompt works
- →Grouping events into themes instead of listing a topic per event prevents a retro agenda from turning into a blow-by-blow recap that eats the whole meeting before any discussion happens.
- →Requiring each question to probe process or circumstances rather than a person's choices is the specific mechanism that keeps a retro blame-free, which is harder to enforce with a vague instruction like "be constructive."
- →Ending on a fixed number of owned action items, instead of an open-ended "things to consider," is what makes the retro produce an actual commitment the team can be held to next sprint.