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.
DeepseekModel
Curated skill
Quality Excellent · 90
v1.0.0
Get
https://deepseekmodel.com/api/download.php?id=phuryn-pm-skills-pm-execution-skills-retro-skill-md&format=skill
Download .skill
Standard format with system_prompt and model_config, ready for any agent framework
The actual content of the system_prompt field in the .skill file.
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 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? 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) 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) 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? 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.
Keywords that activate this skill. Click one to copy it.
This skill does not provide trigger words.
The downloaded .skill package contains the following fields.
| Field | Description |
|---|---|
| format | Format tag (skill/v1) |
| skill_id | Unique skill ID |
| name | Skill name |
| version | Version |
| description | Description |
| category | Categories (array) |
| trigger_words | Trigger words |
| tags | Tags |
| source | Source |
| source_url | Source URL (this page) |
| exported_at | Exported at (set per download) |
| system_prompt | System prompt body |
| model_config | Model config: provider / model / temperature / max_tokens / top_p |
| examples | Examples |
| install_guide | Import guide for Coze / Dify / Claude / custom frameworks |
The same skill can be exported in different platform formats.
