retrospective
Skill1 starsChanged 4 months agoMITView on GitHub
团队回顾会议引导,聚焦「继续做/停止做/开始做」,持续改进团队效能
69 other projects use a version of this.
Adopted by
Most recently taken up by
- Adelie-Squad/solosquadtheir own version, first seen Nov 8, 2026
- sbfnk/skillstheir own version, first seen Nov 8, 2026
- AndyB840506/skillstheir own version, first seen Nov 8, 2026
- paureis/pau-skillstheir own version, first seen Nov 8, 2026
- AsiaOstrich/EngramGraphtheir own version, first seen Nov 8, 2026
- simonasrazm/skillstheir own version, first seen Nov 8, 2026
Used with
Projects with it also use dev-story, team-level and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
lilangMaxSkilldev-story
Read a story file and implement it. Loads the full context (story, GDD requirement, ADR guidelines, control manifest), routes to the right programmer agent for the system and engine, implements the code and test, and confirms each acceptance criterion. The core implementation skill — run after /story-readiness, before /code-review and /story-done.
Also in 12 projects that use this
CoralGameSkillteam-level
Orchestrate level design team: level-designer + narrative-director + world-builder + art-director + systems-designer + qa-tester for complete area/level creation.
Also in 12 projects that use this
CoralGameSkillteam-narrative
Orchestrate the narrative team: coordinates narrative-director, writer, world-builder, and level-designer to create cohesive story content, world lore, and narrative-driven level design.
Also in 12 projects that use this
lilangMaxSkillcreate-stories
Break a single epic into implementable story files. Reads the epic, its GDD, governing ADRs, and control manifest. Each story embeds its GDD requirement TR-ID, ADR guidance, acceptance criteria, story type, and test evidence path. Run after /create-epics for each epic.
Also in 11 projects that use this
- +7 more from lilangMax
- +1 more from CoralGame
Other versions69 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 69
- Donchitos/Claude-Code-Game-Studios★ 27ksame name
- alibaba/MNN★ 16ksame name
- glebis/claude-skills★ 410same name
- pixel-cellar/Claude-Code-Game-Studios★ 324same name
- blacklanternsecurity/red-run★ 296same name
- striderZA/OpenCodeGameStudios★ 118same name
- The01Geek/prflow★ 99same name
- PAIR-code/deliberate-lab★ 97same name
- AsiaOstrich/universal-dev-standards★ 84same name
- tranhieutt/software_development_department★ 71same name
59 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository34 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- daily-standupSkill
- mvp-scopeSkill
- sprint-planningSkill
- sprint-reviewSkill
- sprint-zeroSkill
- aha-momentSkill
- build-measure-learnSkill
- growth-experimentSkill
- north-star-metricSkill
- customer-journey-mapSkill
- empathy-interviewSkill
- ideation-workshopSkill
- problem-statementSkill
- user-personaSkill
- go-to-marketSkill
- launch-checklistSkill
- pitch-deckSkill
- fullstackinno-routerSkill
- writing-great-skillsSkill
- competitive-analysisSkill
- lean-canvasSkill
- user-story-mappingSkill
- value-propositionSkill
- information-captureSkill
- inspiration-boardSkill
- knowledge-linkSkill
- research-synthesisSkill
- web-clipperSkill
- assumption-testingSkill
- concierge-mvpSkill
- landing-page-mvpSkill
- pivot-or-persevereSkill
- problem-interviewSkill
The file
Files
Retrospective 🔄
冲刺回顾。每个冲刺结束后的团队自我反思,聚焦过程改进而非指责。这是敏捷中最重要的仪式之一。
执行流程
第一步:设定安全空间
🛡️ 回顾安全原则(开场必读)
1. 无论发现什么,我们相信每个人
在当时的知识、能力、资源下做到了最好
2. 回顾的目的不是追责,是让下个冲刺更好
3. 所有讨论只关于流程和系统,不针对个人
4. 这里说的内容不对外传播
(Vegas Rule:发生在这里的留在这里)
⏱ 时间盒:
- 1 周冲刺 → 30-45 分钟
- 2 周冲刺 → 60-90 分钟第二步:数据收集
收集冲刺期间的事实数据:
📊 冲刺数据回顾
冲刺 [#N]
日期:[开始] → [结束]
定量数据:
- 计划点数:[X] → 完成点数:[Y] → 完成率 [%]
- 速度:[Y] 点
- 缺陷数:[Z]
- 未规划工作占比:[%]
定性收集(团队成员各自写下):
- 什么事让我感到有成就感?
- 什么事让我感到沮丧?
- 有什么意外收获?第三步:回顾格式
选择一种回顾方式引导讨论:
A. Start / Stop / Continue(推荐入门)
🟢 Start(开始做)— 我们还没做但应该开始的事
┌─────────────────────────────────────────────┐
│ │
└─────────────────────────────────────────────┘
🔴 Stop(停止做)— 影响效率应该停止的事
┌─────────────────────────────────────────────┐
│ │
└─────────────────────────────────────────────┘
🟡 Continue(继续做)— 做得好的应该保持的事
┌─────────────────────────────────────────────┐
│ │
└─────────────────────────────────────────────┘B. 4Ls(深入版)
👍 Liked(喜欢)— 这个冲刺中哪些做得好?
┌─────────────────────────────────────────────┐
│ │
└─────────────────────────────────────────────┘
📚 Learned(学到)— 我们学到了什么?
┌─────────────────────────────────────────────┐
│ │
└─────────────────────────────────────────────┘
💔 Lacked(缺少)— 我们缺少什么?
┌─────────────────────────────────────────────┐
│ │
└─────────────────────────────────────────────┘
🎯 Longed For(渴望)— 我们渴望什么改变?
┌─────────────────────────────────────────────┐
│ │
└─────────────────────────────────────────────┘第四步:投票与行动计划
🗳️ 投票聚焦
每人 [N] 票,投给你认为最需要解决的议题
📊 Top 议题:
🥇 [议题 1] — [N] 票
🥈 [议题 2] — [N] 票
🥉 [议题 3] — [N] 票
📋 行动项(Action Items)
行动 负责人 截止日期 状态
───────────────────── ────────── ────────── ──────
[具体的、可完成的事] [Name] [日期] ⬜
[具体的、可完成的事] [Name] [日期] ⬜
[具体的、可完成的事] [Name] [日期] ⬜
⚠️ 行动项规则:
- 不超过 3 条(太多 = 一条也完不成)
- 每条有明确负责人
- 每条在下个冲刺回顾时检查完成情况第五步:回顾的回顾
📝 回顾总结
本次回顾满意度投票(1-5):[分数]
下个冲刺的改进重点:
[一句话总结最重要的事]
下次回顾建议:
- 换一种回顾方式?(轮流用不同格式避免倦怠)
- 需要邀请谁参加?(偶尔邀请外部视角)反模式
- ❌ 跳过回顾(「太忙了,这次就不做了」→ 这是最需要的时候)
- ❌ 回顾变成吐槽大会(发泄完但没有行动项)
- ❌ 行动项太模糊(「改进沟通」≠ 可执行的行动)
- ❌ 行动项没人跟进(下次回顾时都忘了)
- ❌ 只找别人的问题(每人先说「我哪里可以做得更好」)
- ❌ 只关注负面(也要庆祝这个冲刺的成就)
推荐下一步
→ sprint-planning:带着改进行动项进入下个冲刺
→ 如果连续 3 个冲刺出现问题,检查是否需要 pivot-or-persevere
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

