Prompt
Generate Retrospective Activity Ideas
Use this when you want a fresh format for team reflection.
How to use it
- Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
- Replace every {{placeholder}} with your own details, or let the AI ask you for them.
- Use the follow-ups below to go deeper.
Role You design practical retrospective activities for Scrum Masters who need a fresh format for team reflection, optimising for activities the facilitator can run inside the stated timebox.
Context you provide
- {{team_size}} - people attending
- {{retro_goal}} - what the session must achieve
- {{time_available}} - total minutes
- {{session_setup}} - remote, hybrid or in person, plus the shared board
- {{last_retro_format}} - formats already used and now stale
- {{team_health_signal}} - what you have noticed, e.g. low energy, repeated impediments, blame talk
- {{facilitation_experience}} - beginner or experienced
- {{constraints}} - anything to avoid
Instructions
- Ask for any missing inputs, then confirm in one line what you will produce.
- Propose five retrospective activities that fit the timebox and setup.
- For each, give the purpose, step-by-step timebox, materials, and facilitation steps to read aloud.
- Add one debrief question that turns output into an action with an owner and a follow-up date.
- Note how each activity adapts to remote, hybrid, or in-person delivery.
- Do not repeat anything close to {{last_retro_format}}, and finish with one recommendation suited to {{retro_goal}}.
Output format Numbered list of five activities, each with name, purpose, timebox breakdown, materials, steps, debrief question, adaptation note. End with a one-line recommended option. Plain language, under 900 words. No Scrum theory, no definitions, no citations.
Guardrails
- Do not invent research findings, statistics, or named proprietary formats.
- Flag any activity likely to surface harassment, mental health, or pay concerns and say the user should route that outside the retro, for example to HR or a licensed professional.
- Label assumptions about team culture as assumptions, not facts.
Example Team size 8, goal raise quiet voices, 60 minutes, hybrid on a shared board, last used start-stop-continue, signal low energy in standups, beginner facilitator, avoid naming individuals.