Skip to main content
affpapa.org
RU EN
skill Claude Code CX Codex Cursor GitHub Copilot

retro · phuryn — Claude Code skill: what it does, how to install

Facilitates structured sprint retrospectives, analyzes team performance, and turns feedback into prioritized action items with assigned owners and deadlines.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓ 
npx skills add phuryn/pm-skills --skill retro -a claude-code
Open on GitHub

What retro does

The skill acts as a facilitator for sprint retrospectives. It examines sprint goals, velocity versus commitment, blockers, and team collaboration patterns. When given raw survey notes or chat exports, it groups feedback into recurring themes and detects sentiment trends.

Facilitation follows one of three frameworks: Start / Stop / Continue, 4Ls, or Sailboat. The output is structured as a markdown report with sprint performance indicators, key themes, and an action items table detailing owners, deadlines, and success metrics.

Action items are restricted to 2-3 entries, preventing teams from overcommitting to improvements they will never finish. The skill relies heavily on context, so you need to provide sprint notes or velocity numbers upfront to get useful findings.

What it helps with

  • structure sprint feedback using Start / Stop / Continue, 4Ls, or Sailboat
  • group raw feedback from chat exports and sticky notes into themes
  • assess sprint goal completion and velocity against initial commitments
  • generate prioritized action items with owners, deadlines, and success metrics

Example prompts for the agent

  • Facilitate a retrospective for our latest sprint using the Sailboat format and team-feedback.md
  • Analyze raw survey responses from the team and group them into key themes
  • Generate a retro summary report with action items and follow up on previous retro commitments

How to install retro

1Skills CLI (Vercel)

npx skills add phuryn/pm-skills --skill retro -a claude-code

2Manually: put the files in place

~/.claude/skills/retro/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/retro/

From the same set61

The whole set →
create-prd phuryn This skill builds a lean PRD from an 8-section template. Use it to define a feature, document product requirements, or review an existing PRD. Claude Code CX Codex Cursor +1 10,800installs pre-mortem phuryn Runs a pre-mortem risk assessment on PRDs and launch plans. Catches critical launch blockers, surfaces hidden team assumptions, and maps action items. Claude Code CX Codex Cursor +1 10,200installs outcome-roadmap phuryn Rewrites feature-heavy roadmaps into outcome-focused statements tied to business and customer impact. Helps teams replace rigid feature lists with measurable strategic goals. Claude Code CX Codex Cursor +1 9,900installs prioritization-frameworks phuryn Reference guide to 9 prioritization frameworks: RICE, ICE, Opportunity Score, Kano, MoSCoW and more. Helps you pick the right method, compare approaches, and rank tasks by importance. Claude Code CX Codex Cursor +1 9,900installs strategy-red-team phuryn Stress-tests PRDs, roadmaps, and strategies by attacking load-bearing assumptions before reality does, returning kill criteria and cheap tests. Claude Code CX Codex Cursor +1 9,200installs competitor-analysis phuryn This skill researches direct competitors and compares their positioning, strengths, weaknesses, and pricing. Use it to prepare a competitive brief or find ways to differentiate a product. Claude Code CX Codex Cursor +1 3,800installs business-model phuryn Skill generates a Business Model Canvas with all 9 building blocks: from key partners and activities to channels and revenue streams. Use it to create a business model, document how value flows, or analyze an existing business. Claude Code CX Codex Cursor +1 3,700installs privacy-policy phuryn Skill drafts a detailed privacy policy accounting for GDPR, CCPA, and other regulations. Use it when building a new product, updating data protection docs, or preparing for compliance audits. Claude Code CX Codex Cursor +1 3,500installs

Other versions of retro

retro Matt Pocock Reviews a coding session and suggests changes to the agent environment for later runs. Use it after mistakes, slow repository navigation, or costly tool calls. Claude Code 276,027installs

Similar

apple-reminders Hermes Agent Manages Apple Reminders through the remindctl CLI utility. Enables the assistant to read task lists and schedule items with iCloud sync. Claude Code CX Codex Cursor +1 367installs teams-meeting-pipeline Hermes Agent + Teknium Manages Microsoft Teams meeting summaries, transcript ingestion, and Graph webhook subscriptions. Useful for replaying failed jobs and checking pipeline health. Claude Code CX Codex Cursor +1 365installs find-community slavingia A skill that helps you find the community you already belong to and spot problems worth solving for a minimalist business. Use it when searching for a startup idea or unsure where to start as an entrepreneur. Claude Code CX Codex Cursor +1 2,600installs processize slavingia Turns a software product idea into a manual workflow you can run today. Helps validate value with paying users before writing any code. Claude Code CX Codex Cursor +1 2,500installs gtm-enterprise-onboarding official Smit Patel (https://linkedin.com/in/smitkpatel) A four-phase skill for moving enterprise customers from contract to sustained adoption. Use it to prepare onboarding and address churn risks after go-live. GitHub Copilot 1,600installs gtm-enterprise-account-planning official Smit Patel (https://linkedin.com/in/smitkpatel) This skill helps plan complex enterprise deals, apply MEDDICC, involve the Economic Buyer, and track deal health through a mutual action plan. GitHub Copilot 1,600installs find-skills vercel-labs Discovers and installs agent skills from skills.sh directly inside your coding assistant. Handy when you need domain-specific workflows for a project. Claude Code CX Codex Cursor +1 4,000,000installs grill-me Matt Pocock grill-me interviews you about a plan or design to expose gaps and sharpen decisions. Use it before implementation starts. Claude Code 1,424,476installs

Questions about retro

How to install retro in Claude Code?

Run npx skills add phuryn/pm-skills --skill retro -a claude-code in your terminal.

What does the retro skill do?

It guides sprint retrospectives, analyzes velocity and blockers, and outputs a structured markdown report with prioritized action items.

Which retrospective formats does retro support?

It supports Start / Stop / Continue, 4Ls (Liked, Learned, Lacked, Longed For), and Sailboat.

Source text

SKILL.md · MIT 
---
name: retro
description: "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."
---

## 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**:

   | Priority | Action Item | Owner | Deadline | Success 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.

© phuryn · MIT · phuryn/pm-skills

See also

Project sponsors

Companies that keep this analytics open
Gold sponsor
Nutra.Club

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor