Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.getcore.me/llms.txt

Use this file to discover all available pages before exploring further.

Facilitate a structured retrospective to surface team feedback, celebrate wins, and identify improvements.

​
Tools Required

This skill runs using CORE memory only. No integrations required.

​
Step 1: Gather Sprint Context

Ask for details about the sprint:
  • Sprint duration and dates
  • Sprint goals and what was committed
  • Sprint metrics: velocity, completion %, any blockers
  • Team feedback or survey responses (if available)
  • Status of previous retrospective action items

​
Step 2: Choose a Retro Format

Select a format that fits your team’s needs: Start / Stop / Continue
  • What should we start doing?
  • What should we stop doing?
  • What should we continue doing?
4Ls (Liked / Learned / Lacked / Longed For)
  • What did we like about this sprint?
  • What did we learn?
  • What did we lack?
  • What did we long for (wish we had)?
Sailboat (Metaphorical)
  • Winds: What’s propelling us forward (momentum)?
  • Anchors: What’s holding us back (blockers)?
  • Rocks: What are the risks ahead?
  • Islands: What are our goals/destinations?

​
Step 3: Facilitate Discussion

Guide the team through the chosen format:
  • Use specific sprint examples to ground discussion
  • Capture feedback thematically
  • Separate observations from judgments
  • Focus on behavior and systems, not individuals

​
Step 4: Group Themes

Organize feedback into 3-5 key themes:
  • What patterns emerge?
  • What’s worth celebrating?
  • What needs to change?
  • What’s working well to maintain?

​
Step 5: Prioritize Action Items

Identify 2-3 specific, measurable action items:
  • What: Specific action to take
  • Owner: Who’s accountable
  • Deadline: When to complete
  • Success metric: How we’ll know it worked

​
Step 6: Review Previous Commitments

Check status on action items from previous retrospectives:
  • Were they completed?
  • Did they have the intended impact?
  • Should they carry forward or be retired?

​
Output Format

Sprint Retrospective Summary 📋 Sprint Overview
  • Sprint: [Dates and duration]
  • Sprint goal: [Original goal and outcome]
  • Velocity: [Story points completed vs. committed]
  • Completion rate: [% of committed work done]
🎪 Retro Format Used [Start/Stop/Continue / 4Ls / Sailboat] 💚 What Went Well (Liked / Wind / Continue)
  • [Theme 1]: [Specific examples and why it matters]
  • [Theme 2]: [Specific examples and why it matters]
  • [Theme 3]: [Specific examples and why it matters]
⚠️ What to Improve (Stop / Lacked / Anchors / Rocks)
  • [Issue 1]: [What happened, impact, why it matters]
  • [Issue 2]: [What happened, impact, why it matters]
  • [Issue 3]: [What happened, impact, why it matters]
🚀 Action Items (Specific, Owned, Measurable)
  1. Action: [What to do]
    • Owner: [Person accountable]
    • Deadline: [When]
    • Success metric: [How we’ll know it worked]
  2. Action: [What to do]
    • Owner: [Person accountable]
    • Deadline: [When]
    • Success metric: [How we’ll know it worked]
  3. Action: [What to do]
    • Owner: [Person accountable]
    • Deadline: [When]
    • Success metric: [How we’ll know it worked]
✅ Previous Retrospective Updates
  • [Previous action 1]: [Status: Completed / In-progress / Deferred] — [Impact]
  • [Previous action 2]: [Status: Completed / In-progress / Deferred] — [Impact]

​
Edge Cases

  • Difficult feedback about a person: Redirect to behavior and systems. “How can we structure work so this doesn’t happen again?”
  • Silence or no feedback: Use writing exercise first (silent brainstorm), then discuss. Gives introverts space.
  • Same issues every sprint: Action items aren’t being completed. Pick ONE highest-priority issue and commit to solving it.
  • Too many action items: Prioritize ruthlessly. Focus team on 2-3 items max; defer others.
  • Remote team: Use async brainstorming (Slack/Google Doc) then synthesize together. Video call for discussion.