retro
The retro skill facilitates structured sprint retrospectives using formats like Start/Stop/Continue, 4Ls, or Sailboat to surface team insights. Use this skill when running a retrospective meeting, analyzing sprint performance against goals, processing raw team feedback from surveys or sticky notes, or generating prioritized action items with assigned owners and deadlines to drive continuous improvement between sprints.
git clone --depth 1 https://github.com/phuryn/pm-skills /tmp/retro && cp -r /tmp/retro/pm-execution/skills/retro ~/.claude/skills/retroSKILL.md
## 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.
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.
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.
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.
Identify the first beachhead market segment for a product launch. Evaluates segments against burning pain, willingness to pay, winnable market share, and referral potential. Use when choosing a first market, targeting an initial customer segment, or planning market entry strategy.
Design experiments to test assumptions for an existing product — prototypes, A/B tests, spikes, and other low-effort validation methods. Use when validating assumptions, testing feature ideas cheaply, or planning product experiments.
Design lean startup experiments (pretotypes) for a new product. Creates XYZ hypotheses and suggests low-effort validation methods like landing pages, explainer videos, and pre-orders. Use when validating a new product idea, creating pretotypes, or testing market demand.
Brainstorm product ideas for an existing product using multi-perspective ideation from PM, Designer, and Engineer viewpoints. Use when generating new feature ideas, brainstorming solutions for an identified opportunity, or ideating with a product trio.
Brainstorm feature ideas for a new product in initial discovery from PM, Designer, and Engineer perspectives. Use when starting product discovery for a new product, exploring features for a startup idea, or doing initial ideation.