Facilitate a Sprint Retrospective

This prompt turns the model into an agile coach and produces a complete, timeboxed 60-minute retro kit tailored to your sprint's actual goals and outcomes — agenda, custom discussion prompts, an action-item template, and an opening energizer. Reach for it when you're the one running the retro and want it to feel intentional rather than 'so... what went well?' on repeat. Feeding it real sprint context is what makes the prompts land on what your team actually lived through.

What you can expect back

Energizer (5 min): "One word" — each person drops a single word in chat describing the sprint, then read them aloud. Fast, honest, sets the tone.

Agenda (60 min)
- 0–05 Energizer + ground rules
- 05–10 Recap goal vs. outcome (checkout v2, +3 days)
- 10–25 What went well (round-robin)
- 25–45 What could improve + group themes
- 45–58 Vote on top 2 themes, draft action items
- 58–60 Close and confirm owners

What went well — prompts
- How did the team respond when the gateway outage hit mid-sprint?
- What helped us ship the hotfixes quickly once we found them?
- Where did someone step up that we should call out?

What could improve — prompts
- When did we first sense scope was growing, and why didn't we flag it?
- What would have caught the gateway risk before release day?
- How did the morale dip start, and what would have helped sooner?

Action-item template
- Action | Owner | Due date | How we'll know it worked
- e.g. "Add a pre-release dependency-health check | Priya | next sprint planning | check runs in CI on every release branch"

Illustrative example — your results will vary by tool and inputs.

Get sharper results

• 01Include the rough team size and whether it's remote or in-person so the activities fit the format — a round-robin works differently for 5 people in a room than 12 on a call.
• 02Name the morale or conflict undercurrent honestly in the context, and the model will write 'what could improve' prompts that open the real conversation instead of safe ones.
• 03Ask for the prompts to be psychologically safe and blame-free if tensions are high, so improvement questions target the system, not specific people.
• 04Request a parking-lot mechanism in the agenda so off-topic but important issues get captured without derailing the timebox.
• 05Have it limit the team to two action items, since retros that generate eight items usually deliver none — fewer, owned commitments stick.

Adapt it for your case