AutoGineer
Generated banner for Retro
Generated logo for Retro

Retro

Pawel HurynCommunityCreated by Pawel Huryn

  • Skill
  • Workflow
  • Business and productivity
  • MIT
  • No issues found
Download ZIP

From the author

Facilitate a structured sprint retrospective — what went well, what didn't, and prioritized action items with owners and deadlines. Use when running a retrospective, reflecting on a sprint, creating action items from team feedback, or learning how to run effective retros.
— the description by Pawel Huryn

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

The retro skill provides a structured framework for conducting team retrospectives. It guides users through selecting a reflection format, analyzing sprint data, synthesizing team feedback into themes, and establishing clear, measurable action items with assigned owners and deadlines. The skill emphasizes a constructive, blame-free environment focused on continuous improvement.

What it does

  • Facilitates retrospectives using established formats like Start/Stop/Continue, 4Ls, or Sailboat.
  • Analyzes raw team feedback to identify recurring themes and sentiment patterns.
  • Evaluates sprint performance metrics including goal achievement and velocity.
  • Generates prioritized, actionable improvement plans with owners and success metrics.
  • Tracks progress on action items carried over from previous retrospectives.
  • Produces a structured markdown summary of the retrospective findings.

When to use it

  • At the conclusion of a sprint to reflect on team performance.
  • When the team needs a structured way to process feedback and identify process improvements.
  • When previous retrospectives have failed to result in concrete action items.
  • When you need to facilitate a team discussion about blockers and successes.

Advantages

  • Provides a consistent, repeatable structure for team reflection.
  • Helps move from vague complaints to specific, measurable action items.
  • Ensures accountability by assigning owners and deadlines to improvements.
  • Maintains a constructive tone that focuses on growth rather than blame.

Usage examples

“Run a 4Ls retrospective for our last sprint. Here is the team feedback: [pasted feedback].”
The agent will categorize the feedback into Liked, Learned, Lacked, and Longed For, analyze the themes, and propose a set of prioritized action items.
“Facilitate a Sailboat retro for our team. We missed our sprint goal and want to identify why.”
The agent will guide the team through identifying the Wind, Anchors, Rocks, and Island, followed by a summary of performance and actionable steps to address the blockers.

Install

  1. Download the skill as a ZIP:

    https://autogineer.com/agent-skills/phuryn/retro/download

  2. Unzip it into the cross-client skills folder of your project:

    mkdir -p .agents/skills && unzip retro.zip -d .agents/skills

Documentation by Pawel Huryn

Sprint Retrospective Facilitator

Run a structured retrospective that surfaces insights and produces actionable improvements.

Context

You are facilitating a retrospective for $ARGUMENTS.

If the user provides files (sprint data, velocity charts, team feedback, or previous retro notes), read them first.

Instructions

  1. Choose a retro format based on context (or let the user pick):

    Format A — Start / Stop / Continue:

    • Start: What should we begin doing?

    • Stop: What should we stop doing?

    • Continue: What's working well that we should keep?

    Format B — 4Ls (Liked / Learned / Lacked / Longed For):

    • Liked: What did the team enjoy?

    • Learned: What new knowledge was gained?

    • Lacked: What was missing?

    • Longed For: What do we wish we had?

    Format C — Sailboat:

    • Wind (propels us): What's driving us forward?

    • Anchor (holds us back): What's slowing us down?

    • Rocks (risks): What dangers lie ahead?

    • Island (goal): Where are we trying to get to?

  2. If the user provides raw feedback (e.g., sticky notes, survey responses, Slack messages):

    • Group similar items into themes

    • Identify the most frequently mentioned topics

    • Note sentiment patterns (frustration, energy, confusion)

  3. Analyze the sprint performance:

    • Sprint goal: achieved or not?

    • Velocity vs. commitment (over-committed? under-committed?)

    • Blockers encountered and how they were resolved

    • Collaboration patterns (what worked, what didn't)

  4. Generate prioritized action items:

    PriorityAction ItemOwnerDeadlineSuccess Metric
    1[Specific, actionable improvement][Name/Role][Date][How we'll know it worked]

    • Limit to 2-3 action items (more won't get done)

    • Each must be specific, assignable, and measurable

    • Reference previous retro actions if available — were they completed?

  5. Create the retro summary:

    ## Sprint [X] Retrospective — [Date]

### Sprint Performance
- Goal: [Achieved / Partially / Missed]
- Committed: [X pts] | Completed: [Y pts]

### Key Themes
1. [Theme] — [summary]

### Action Items
1. [Action] — [Owner] — [By date]

### Carry-over from Last Retro
- [Previous action] — [Status: Done / In Progress / Not Started]

Save as markdown. Keep the tone constructive — the goal is improvement, not blame.

Files

Requirements and compatibility

Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Security

No issues found by our static scan· No issues found

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Attribution and licence

Created by
Pawel Huryn
Publisher
Pawel Huryn (Community)
Source
phuryn/pm-skills · pm-execution/skills/retro · commit 2a12295
Licence
MIT License (redistribution allowed)
  • LICENSE (added by AutoGineer from LICENSE)
  • ATTRIBUTION.md (written by AutoGineer)
Synced

AutoGineer is not affiliated with or endorsed by Pawel Huryn or Pawel Huryn.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download retro.zip