Sprint Retrospective Notes and Action Items for Jira
Turn retrospective input into themes and trackable actions.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
Summarise this sprint retrospective: [RETRO_NOTES]. Format used (for example start/stop/continue, 4Ls, mad/sad/glad): [RETRO_FORMAT]. Team size: [TEAM_SIZE]. Actions left open from the last retrospective: [PREVIOUS_ACTIONS]. Group comments into themes with counts of how many people raised each, without naming individuals, and identify the two themes with the most energy. For each, propose one concrete experiment for the next sprint with an owner placeholder, a measure and a review date. Review last time's actions: done, partly done or dropped, with a reason. Keep the tone blame-free and do not invent quotes. Output a Confluence-ready page in Markdown and up to three Jira issues (summary and description) for the actions, labelled retro-action. Count a theme only once per person, and write 'one voice' beside a theme raised by a single person so it is not ranked with the repeated ones. Write each experiment small enough to try in one sprint, with a check at the next retrospective: what will we look at, and what result would make us keep it? Keep the actions to three or fewer, because teams rarely finish more, and list any comment you did not use with the reason. Write the Confluence page so it can be read in two minutes by someone who was not there.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.