Business
Retrospective Prompt Generator
Used by developers, writers, and creators worldwide.
A retrospective prompt generator produces discussion prompts to run a sprint or project retrospective with your team. A good retro is where teams actually improve — but they often stall into awkward silence or the same two people talking, and "so, how did the sprint go?" rarely sparks honest reflection. This tool gives you focused prompts in the proven start/stop/continue and went-well/slowed-us-down shapes, so everyone has something concrete to respond to. Generate a set, work through a few as a team, and turn the answers into one or two real action items. It is ideal for agile retrospectives, project post-mortems, and any team that wants to get better deliberately. The point is honest reflection and a small change you actually make next time — not a long list nobody revisits.
Loading usage…
Free forever — no account required
How to use
- Choose your options above
- Click Generate
- Copy your result
Detailed instructions
- Choose how many prompts you want.
- Click Generate to produce retrospective prompts.
- Work through a few as a team.
- Capture one or two concrete action items.
Use Cases
- •Running an agile sprint retrospective
- •A project post-mortem or wrap-up
- •Getting past awkward retro silences
- •Structuring a team improvement session
- •Turning reflection into concrete action items
Tips
- →Make it safe to be honest — no blame.
- →End with specific actions, not a long wishlist.
- →Rotate who facilitates to keep it fresh.
- →Revisit last retro's actions before starting.
FAQ
what is a retrospective
A retrospective is a regular team meeting, common in agile, where the team reflects on how recent work went and decides what to improve. It focuses on the process and ways of working, not on individual blame, and ends with concrete actions.
how do i run a good retrospective
Use focused prompts so everyone has something to respond to, make it safe to be honest, and end with one or two specific action items you will actually do. Frameworks like start/stop/continue keep the conversation structured and productive.
what questions should i ask in a retro
Ask what went well, what slowed the team down, and what to start, stop, or continue. Pair these with a forward-looking question about risks or one change to make. Specific prompts draw out more than a vague "how did it go?"