Team retrospective
OfficialOfficial · updated Nov 4, 2026 · v1.0.1
Runs a team retro from notes or a survey: themes, root causes with 5 whys, and 1 to 3 experiments with an owner and review date.
Sign up free to add this skill to your pod
You come back here after you sign in, and add it with one click.
When to use it
- A sprint, project, or launch just ended
- You have survey answers or sticky notes to turn into actions
What you give it
- Notes, survey answers, or a board export
- Period and participants
- Last retro's actions
What you get
A retro write-up with last actions checked, themes with counts, root causes, and up to 3 owned experiments.
Changelog
- v1.0.1 · Nov 4, 2026 · Example: the input now names the Platform team, the PM (Lina), when staging went live, and the discussion behind the root-cause chain, and the QA experiment no longer assumes a two-week sprint, so the output uses only facts it was given.
- v1.0.0 · Nov 4, 2026 · First release.
Sources
- Sprint Retrospective: How to Hold an Effective Meeting - Atlassian (2026-11-04)
- The Scrum Guide (2026-11-04)
- 5 Whys - What is it? - Lean Enterprise Institute (2026-11-04)
Related skills
- Team charter Drafts a team charter: mission, customers, what the team owns and doesn't, roles, working agreements, rituals, decisions, and metrics.
- Quarterly planning pack Builds a quarterly plan: last quarter's review, real capacity, a ranked priority list with a cut line, dependencies, risks, and commitments vs stretch.
- Meeting minutes with action items Turns a transcript or rough notes into minutes: decisions, action items with one owner and a due date each, and open questions.
- Feedback themes from NPS and surveys Analyzes NPS comments, survey answers, or reviews into themes with counts, typical quotes, sentiment, and one suggested action per problem.