Dev Team Retrospective Builder

The problem

Sprint retrospectives often devolve into vague complaints, blame-shifting, or generic action items like "communicate better." Technical leads struggle to extract actionable experiments from messy Slack notes, incident logs, and verbal feedback.

What it does

• Clusters raw sprint notes, blockers, and incident logs into objective, blameless themes.
• Generates root-cause discussion prompts that focus on process gaps rather than individual mistakes.
• Designs time-boxed meeting agendas tailored to your team's available schedule.
• Builds structured improvement experiments with clear owners, success metrics, and review dates.
• Audits existing retrospective documents to remove blame language and sharpen vague action items.

Why this beats prompting it yourself

Standard LLM prompts often produce generic corporate fluff or overly critical performance critiques. This skill uses a specialized framework to ensure every output is blameless, focuses on small-scale experiments, and produces a structured action register that is actually usable in a tracking tool.

Use cases

• Converting rough bullet points from a chaotic release into a structured learning session.
• Facilitating a neutral, data-driven discussion after a major production incident.
• Cleaning up low-quality retro notes to make them professional for stakeholder reporting.
• Scaffolding a 45-minute agile ceremony for a remote engineering team.

Known limitations

Does not integrate directly with Jira or Linear APIs. Requires manual input of notes and does not replace a human facilitator for high-conflict interpersonal issues.