Login
phuryn/pm-skills1 file

Retro

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.

Use this skillView repositoryView on skills.sh
Specification
Skill ID
phuryn/pm-skills/retro
Publisher
phuryn
Repository
pm-skills
Installs
0
Files
1
Synced
Sep 23, 2026
How to use it

Open any RiverX project, open the Skills panel in the chat, and search for this identifier. The files are fetched from the source repository at install time.

phuryn/pm-skills/retroInstalls these files
  • SKILL.md

What this skill tells the agent

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?
  1. 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)
  1. 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)
  1. 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?
  1. 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.

More from phuryn

phuryn/pm-skills

Ab Test Analysis

Analyze A/B test results with statistical significance, sample size validation, confidence intervals, and ship/extend/stop recommendations. Use when evaluating experiment results, checking if a test reached significance, interpreting split test data, or deciding whether to ship a variant.

phuryn/pm-skills

Analyze Feature Requests

Analyze and prioritize a list of feature requests by theme, strategic alignment, impact, effort, and risk. Use when reviewing customer feature requests, triaging a backlog, or making prioritization decisions.

phuryn/pm-skills

Ansoff Matrix

Generate an Ansoff Matrix analysis mapping growth strategies across market penetration, market development, product development, and diversification. Use when considering growth options, planning market expansion, or evaluating strategic growth paths.

Use this skill in a project

Open any RiverX project, search the Skills panel for phuryn/pm-skills/retro, and install it in one click.

Use this skill