AI驱动的迭代回顾会引导者 - 结构化敏捷回顾会议工具

retro by phuryn/pm-skills

300 周安装量

9,200 GitHub Stars

GitHub

安装命令

npx skills add https://github.com/phuryn/pm-skills --skill retro

方法论项目管理团队沟通

🇨🇳中文介绍

迭代回顾会引导者

运行一个结构化的回顾会议，以发掘洞见并产生可执行的改进措施。

上下文

你正在为 $ARGUMENTS 引导一场回顾会议。

如果用户提供了文件（迭代数据、速率图、团队反馈或之前的回顾笔记），请先阅读它们。

指令

选择一个回顾格式（根据上下文或让用户选择）：

格式 A — 开始 / 停止 / 继续 :

 * **开始** : 我们应该开始做什么？
 * **停止** : 我们应该停止做什么？
 * **继续** : 哪些方面运作良好，我们应该继续保持？

格式 B — 4Ls（喜欢 / 学到 / 缺乏 / 渴望） :

 * **喜欢** : 团队喜欢什么？
 * **学到** : 获得了哪些新知识？
 * **缺乏** : 缺少了什么？
 * **渴望** : 我们希望能拥有什么？

格式 C — 帆船 :

 * **风（推动我们前进）** : 是什么在推动我们前进？
 * **锚（阻碍我们）** : 是什么在拖慢我们的速度？
 * **礁石（风险）** : 前方存在哪些危险？
 * **岛屿（目标）** : 我们试图到达哪里？

2. 如果用户提供了原始反馈（例如，便利贴、调查回复、Slack 消息）：

 * 将相似的项目归类为主题
 * 识别最常被提及的话题
 * 注意情绪模式（挫败感、活力、困惑）

广告位招租

在这里展示您的产品或服务

触达数万 AI 开发者，精准高效

联系我们

优先级	行动项	负责人	截止日期	成功指标
1	[具体、可执行的改进措施]	[姓名/角色]	[日期]	[我们如何知道它有效]

🇺🇸English

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?

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.

Weekly Installs

227

Repository

phuryn/pm-skills

GitHub Stars

8.1K

First Seen

Mar 4, 2026

Security Audits

Gen Agent Trust HubPass SocketPass SnykPass

Installed on

codex214

opencode212

github-copilot211

cursor211

gemini-cli211

kimi-cli210