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.
MCP get_skill({ skillId: "retro-f0b56c47" })Use this skill with your agent
Create a free account and connect via MCP
## 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.
Related Skills
More skills in Business, Marketing & Sales
Ab Testing
When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program," or "experiment playbook." Use this whenever someone is comparing two approaches and wants to measure which performs better, or when they want to build a systematic experimentation practice. For tracking implementation, see analytics. For page-level conversion optimization, see cro.
Ab Test Setup
When the user wants to plan, design, or implement an A/B test or experiment. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "conversion experiment," "statistical significance," or "test this." For tracking implementation, see analytics-tracking.
Ab Test Setup
Ab Test Setup linked from Corey Haines marketing skills, with the upstream skill instructions available on GitHub.
Ab Test Store Listing
When the user wants to A/B test App Store product page elements to improve conversion rate. Also use when the user mentions "A/B test", "product page optimization", "test my screenshots", "test my icon", "conversion rate optimization", "CPP", or "custom product pages". For screenshot design, see screenshot-optimization. For metadata optimization, see metadata-optimization.
Account Research
Research a company or person and get actionable sales intel. Works standalone with web search, supercharged when you connect enrichment tools or your CRM. Trigger with "research [company]", "look up [person]", "intel on [prospect]", "who is [name] at [company]", or "tell me about [company]".
Account Research
Research a company using Common Room data. Triggers on 'research [company]', 'tell me about [domain]', 'pull up signals for [account]', 'what's going on with [company]', or any account-level question.
Explore Other Categories
Skills from other categories with shared topics
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.
Cohort Analysis
Perform cohort analysis on user engagement data — retention curves, feature adoption trends, and segment-level insights. Use when analyzing user retention by cohort, studying feature adoption over time, investigating churn patterns, or identifying engagement trends.
Create Prd
Create a Product Requirements Document using a comprehensive 8-section template covering problem, objectives, segments, value propositions, solution, and release planning. Use when writing a PRD, documenting product requirements, preparing a feature spec, or reviewing an existing PRD.