Azure DevOps Retrospective Actions as Work Items
Convert retrospective output into trackable items.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
Convert this retrospective into Azure DevOps work items: [RETRO_NOTES]. Sprint: [SPRINT]. Team size: [TEAM_SIZE]. Previous actions: [PREVIOUS_ACTIONS]. First review the previous actions. Group the comments by theme and count them, pick the top two themes, and propose up to three small actions the team can finish in one sprint, each under two days of effort. For each action give a title, description, owner placeholder, acceptance criteria, how we will know it worked as a question for the review date (for example did build time fall below ten minutes?), a review date at the start of the next retrospective, a tag (retro-action) and an iteration. Keep the tone blame-free and do not include the names of people who made comments. List any comment you did not use with the reason. Keep the whole output under 300 words, with a one-line summary for the team channel. Put the actions in a table I can copy into the backlog, with one row per action. If no theme stands out, say so and propose one experiment instead of three actions.
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.