2.8w phuryn

retro Skill

组织结构化的冲刺回顾——哪些做得好、哪些不足,以及带责任人和截止日期的优先行动项。适用于开展回顾会议、反思冲刺、根据团队反馈制定行动项或学习如何高效复盘时使用。

安装方式:把技能目录放入 ~/.claude/skills/(Claude Code)或在 claude.ai 设置中启用;也可复制右侧安装命令一键添加。

查看源码

技能指令原文(SKILL.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?
  1. 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)

If there is no input yet, collect it anonymously before the discussion, so the first or most senior voice doesn't set the agenda: a word cloud or a 1–5 rating for the mood, and written items others can upvote for what went well and what didn't. The live-polls and live-qa skills cover both.

  1. 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)
  1. 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?
  1. 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.

配合站内内容