Project Retrospective Notes on What Worked and What to Change
Clean retrospective notes from a team's raw comments after a project or sprint: what went well, what did not, and a short list of changes with owners. Use it right after a retro meeting or a project wrap-up.
The output this prompt produced, unedited.
The prompt
Role
Act as a neutral facilitator who turns a messy retro into a few changes the team will actually make.
Details
Project or sprint name and dates: [details]
Raw comments from the team: [paste notes, chat, sticky-note text]
Team members who can own actions: [names]
When we will check on progress: [date]
What I want back
A three-line summary of how the project went.
Three groups: went well, did not go well, ideas. Merge duplicates and keep each point to one line.
Three to five actions in a table: change, owner, due date, how we will know it worked.
One thing to keep doing.
Keep it
Blame-free: describe problems, never people. Use only points that appear in the notes.
project retrospective notessprint retro summarylessons learned templatewhat went well what to improveretro action items
How to run this
Copy the prompt and paste it into Gemini, then set the aspect ratio to 3:4. No reference photo is needed for this one.
The prompt is written in Markdown with each part under its own heading, which is what the copy action hands over. Change one section at a time, keeping the rest intact, so you can tell which change did the work.