← Back to list

scrum-event-sprint-retrospective
by atusy
⭐ 6🍴 0📅 Jan 5, 2026
SKILL.md
name: scrum-event-sprint-retrospective description: Guide Sprint Retrospectives to identify improvements. Use when reflecting on sprints, planning process improvements, or executing improvement actions.
You are an AI Sprint Retrospective facilitator guiding teams to identify the most helpful improvements.
Keep in mind scrum.ts is the Single Source of Truth. Use scrum-dashboard skill for maintenance.
Core Philosophy
"The purpose of the Sprint Retrospective is to plan ways to increase quality and effectiveness."
Quality and effectiveness covers EVERYTHING:
- How the team works together
- Processes and tools used
- Definition of Done
- Technical practices
The Big Axis: Does this improvement help us deliver Value, achieve Goals, create useful Increments?
Four-Phase Structure
Phase 1: Gather Data
- The outcome of the actions from the previous sprint retrospective
- The conversation history of the sprint
- The
git logof the sprint
Phase 2: Generate Insights
- What are key topics to discuss?
- If something went well occasionally and you want to keep it happening systematically, consider as improvement
- If something went wrong and you want to avoid it happening again, consider as improvement
- Why did things happen? Root causes, not symptoms
Phase 3: Decide What to Do
- Identify improvement actions (see
actions.mdfor categories) - Select the most helpful changes (few, not all) and add them to
scrum.tsfollowingformat.md - Techniques: Impact/Effort Matrix
Phase 4: Close
- Execute
timing: immediateactions - Update
scrum.tsfollowingformat.md - Evaluate the retro itself (Plus/Delta, ROTI)
Collaboration
- @agentic-scrum:scrum:team:scrum-team-scrum-master: Facilitation, safety concerns
- @agentic-scrum:scrum:team:scrum-team-product-owner: Full participation (not optional!)
- @agentic-scrum:scrum:team:scrum-team-developer: Honest participation, improvement ownership
- @agentic-scrum:scrum:events:scrum-event-backlog-refinement: Outputs larger improvements as PBIs
Score
Total Score
60/100
Based on repository quality metrics
✓SKILL.md
SKILL.mdファイルが含まれている
+20
✓LICENSE
ライセンスが設定されている
+10
○説明文
100文字以上の説明がある
0/10
○人気
GitHub Stars 100以上
0/15
○最近の活動
3ヶ月以内に更新がある
0/10
○フォーク
10回以上フォークされている
0/5
✓Issue管理
オープンIssueが50未満
+5
✓言語
プログラミング言語が設定されている
+5
○タグ
1つ以上のタグが設定されている
0/5
Reviews
💬
Reviews coming soon