‹ 首页

retro

@phuryn · 收录于 1 周前 · 上游提交 1 周前★ 社区精选

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.

场景冲刺回顾团队复盘行动项跟进

适合你，如果你需要带领团队做冲刺回顾并产出可执行的任务

/ 下载安装
https://github.com/phuryn/pm-skills/tree/main/pm-execution/skills/retro ↗
/ 通过 npx 安装 校验哈希
npx oh-my-skill add phuryn/pm-skills/retro
/ 通过 bash 安装
curl -fsSL https://oh-my-skill.com/install.sh | bash -s -- phuryn/pm-skills/retro
/ 已经装过?验证本机副本,不用重装
npx oh-my-skill verify phuryn/pm-skills/retro
安装目标可用 --agent / --scope 或 --to 明确指定;省略时只会在唯一已存在的 agent 目录上自动选择,零命中或多命中会停止并提示。content_hash 缺失或不一致均拒装。
23265GitHub stars
~585上下文体积 · 单文件
索引托管

怎么用

商店整理自技能原文 · 版本 18468a9 · 表述以原文为准
它做什么

装上后，Claude 会引导你完成一次结构化的冲刺回顾会议。它会帮你选择回顾格式（如开始/停止/继续、4Ls、帆船法），分析团队反馈和冲刺数据，生成带负责人和截止日期的优先改进事项，并输出一份回顾总结。

什么时候触发

当你需要运行冲刺回顾、反思一个冲刺、从团队反馈中创建行动项，或学习如何有效进行回顾时触发。

装好后可以这样说
Claude 会引导你完成该格式的回顾。
Claude 会分析你提供的反馈并归纳主题。
Claude 会输出包含行动项和指标的总结。
技能原文 SKILL.md作者撰写 · MIT · 18468a9
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):
  2. Group similar items into themes
  3. Identify the most frequently mentioned topics
  4. Note sentiment patterns (frustration, energy, confusion)
  1. Analyze the sprint performance:
  2. Sprint goal: achieved or not?
  3. Velocity vs. commitment (over-committed? under-committed?)
  4. Blockers encountered and how they were resolved
  5. 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.

按 MIT 许可原样转载,未经改动 · 在 GitHub 查看 →

评论

登录即可评论;带「已验证安装」的,是发布者名下有本店的安装或持有记录。
…