Review a team sprint with AI
Group comments from the last sprint into a few issues the team can act on. Give each agreed change an owner, a deadline and a way to tell if it helped.
Review a team sprint with AI by looking at the last set of promises before asking for another round of ideas. If the team agreed to hand designs over earlier, did anyone actually try it? An honest answer tells you more than another list of complaints about timing.
The retro skill groups feedback around shared experiences. A comment can remain anonymous even when someone volunteers to own the resulting change. It also offers different discussion formats: what to start or stop, what people learned, or what helped and hindered progress towards the goal.
What it does
- Choose a format for a difficult or uneventful sprint
- Group related comments without naming their authors
- Compare the agreed sprint goal with the outcome
- Identify recurring blockers across meeting notes
- Attach a deadline and a success measure to each agreed action
Install and use
- Use the skill in a compatible agent with authorised notes. Remove identifying details where practical. Analysing a supplied document needs no polling account; live collection requires separate tools.
- Ask: “Group these anonymous notes by theme. Which handovers caused delays? Suggest two changes we can test without assigning blame.”
- Check the themes with the team. Ask a volunteer to take each agreed change and set a date to review it.
FAQ
Source
Made by Paweł Huryn. Original skill: retro, published on GitHub under the MIT licence.
View on GitHub