菜单
[UDS] Guide structured team retrospectives for Sprint and Release cycles. Use when: sprint end, release post-mortem, iteration review, process improvement. Keywords: retrospective, retro, sprint review, lessons learned, action items.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/AsiaOstrich/universal-dev-standards --skill retrospective命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
[UDS] 以 Claude 原生 Agent tool 编排多任务执行计划（DAG-based，无外部引擎）。 Use when: executing a plan.json file with parallel/sequential task dependencies. Keywords: orchestrate, plan, execute, DAG, task plan, 编排, 执行计划, 并行.
[UDS] 从 Spec 文档、OpenSpec 变更或自由文本需求生成 plan.json。 Use when: converting specifications into executable task plans for /orchestrate. Keywords: plan, spec, task plan, 计划, 规格, 任务, plan.json, DAG.
[UDS] AI 辅助 git push 安全层：质量门禁 + 协作护栏。 Use when: pushing commits, force pushing, pushing to protected branches, pushing feature branches. Keywords: git push, force push, protected branch, quality gate, push receipt, PR automation, 推送, 保护分支, 质量门禁.
正在显示 SKILL.md
基于 SOC 职业分类
| name | retrospective |
| scope | universal |
| description | [UDS] Guide structured team retrospectives for Sprint and Release cycles. Use when: sprint end, release post-mortem, iteration review, process improvement. Keywords: retrospective, retro, sprint review, lessons learned, action items. |
| allowed-tools | Read, Write, Glob, Grep |
| argument-hint | [sprint | release | actions | --technique starfish] |
Language: English | 繁體中文
Guide structured team retrospectives to identify improvements and track action items. Support Sprint and Release retrospective types with multiple facilitation techniques.
引導結構化的團隊回顧，識別改善機會並追蹤行動項目。支援 Sprint 和 Release 回顧類型，提供多種引導技法。
PREPARE ──► GATHER ──► ANALYZE ──► DECIDE ──► TRACK
準備資料 蒐集意見 分析歸納 決定行動 追蹤落實
Gather data from git log, metrics, and issue tracker to ground the discussion.
從 git log、指標和 issue tracker 蒐集數據作為討論基礎。
Collect perspectives using a structured technique.
使用結構化技法蒐集團隊觀點。
Group items and identify patterns.
分組歸納並識別模式。
Select top 1-3 improvements as action items.
選出前 1-3 項改善作為行動項目。
Review previous actions and track new ones.
檢視過去的行動項目並追蹤新項目。
| Type | When | Duration | Focus | 焦點 |
|---|---|---|---|---|
| Sprint | End of iteration | 30-60 min | Process, collaboration, tools | 流程、協作、工具 |
| Release | After release | 60-90 min | Quality, metrics, cross-team | 品質、指標、跨團隊 |
| Technique | Best For | Structure | 結構 |
|---|---|---|---|
| Start-Stop-Continue | Quick, default | Start / Stop / Continue | 開始 / 停止 / 繼續 |
| Starfish | Nuanced analysis | More / Keep / Less / Start / Stop | 更多 / 保持 / 減少 / 開始 / 停止 |
| 4Ls | Team building | Liked / Learned / Lacked / Longed for | 喜歡 / 學到 / 缺少 / 渴望 |
| Sailboat | Visual, creative | Wind / Anchor / Rocks / Island | 風 / 錨 / 礁石 / 島嶼 |
| Command | Action | 說明 |
|---|---|---|
/retrospective | Interactive Sprint retrospective (default) | 互動式 Sprint 回顧 |
/retrospective sprint | Sprint retrospective | Sprint 回顧 |
/retrospective release | Release retrospective with metrics | Release 回顧（含指標） |
/retrospective actions | List open action items | 列出未完成行動項目 |
/retrospective --technique starfish | Use specific technique | 使用指定技法 |
| Field | Description | 說明 |
|---|---|---|
| Action | Specific description | 具體描述 |
| Owner | Single person responsible | 單一負責人 |
| Due Date | Target completion | 預計完成日 |
| Status | Open → In Progress → Done | 狀態 |
docs/retrospectives/
├── RETRO-2026-03-15-sprint-12.md
├── RETRO-2026-03-26-release-v5.1.0.md
└── README.md # Index (optional)
| Skill | Integration | 整合方式 |
|---|---|---|
/metrics | Pull metrics data into release retrospective | 引用指標數據 |
/incident | Post-incident, suggest team retrospective | 事故後建議回顧 |
/adr | If architecture issues found, suggest ADR | 識別架構問題時建議 ADR |
/commit | Commit retro report with docs(retro): | 提交回顧報告 |
After /retrospective completes:
Retrospective complete. Suggested next steps:
- Commit the retrospective report:
/commit- Create ADRs for architectural decisions identified:
/adr- Track action items in your issue tracker
- Schedule next retrospective
回顧完成。建議下一步：
- 提交回顧報告：
/commit- 為識別的架構決策建立 ADR：
/adr- 在 issue tracker 中追蹤行動項目
- 排定下次回顧
When /retrospective is invoked:
docs/retrospectives/ for previous actionsdocs/retrospectives/RETRO-YYYY-MM-DD-[type].mdWhen /retrospective actions is invoked:
docs/retrospectives/ for all retro files