Sprint retrospective

1---
2name: "sprint-retro"
3title: "Sprint retrospective"
4description: "Synthesises team input into a structured retro with clear action items."
5audience: "internal"
6format: "bullets"
7tone: "direct"
8triggers:
9  - "sprint retro"
10  - "retro summary"
11  - "turn this into our retro notes"
12---
13
14## Overview
15This skill handles **Sprint retrospective**. It produces bullet points output in a direct voice, written for internal team.
16When this skill is triggered, expect the user to provide: **Retro notes, board exports, or team feedback from the sprint**. If this input has not been provided, ask for it before proceeding — do not guess or use placeholder data.
17## Process
181. Summarise the sprint outcome in one bullet.. Confirm this step is complete before moving on.
192. Group feedback into what worked, what did not, and what to change next.
203. End with concrete action items and owners for the next sprint.
21## Quality Standards
22- Use team-familiar terminology
23- Each bullet must be actionable or informational — no filler
24- Include owners and deadlines where relevant
25- Keep total length under 300 words
26
27## What to Avoid
28
29- Do not turn the retro into blame language or hide unresolved friction.
30
31## Example Triggers
32- "sprint retro"
33- "retro summary"
34- "turn this into our retro notes"