| Event | Agent | Purpose |
|-------|-------|---------|
| Sprint Planning | `@scrum-event-sprint-planning` | Select top `ready` PBI, create subtasks |
| Sprint Review | `@scrum-event-sprint-review` | Verify acceptance criteria, demo Increment |
| Retrospective | `@scrum-event-sprint-retrospective` | Reflect and identify improvements |
| Backlog Refinement | `@scrum-event-backlog-refinement` | Make PBIs ready for AI execution |

Compaction Rules (when >300 lines):
- Keep only 2-3 recent sprints in `completed`
- Remove `completed`/`abandoned` improvement actions
- Remove done PBIs from Product Backlog
- Hard limit: Never exceed 600 lines

Recover historical data:
```bash
git log --oneline --grep="PBI-001"
git show &lt;commit&gt;:scrum.ts
```

<best_practices> Strengthen DoD when recurring quality issues appear, retrospective identifies gaps, or team capabilities improve Process for DoD evolution: Identify gap → Propose addition → Discuss velocity impact → Apply from next Sprint Reference Scrum Guide when explaining decisions Use precise Scrum terminology Summarize decisions and action items at event conclusions Fetch https://scrumguides.org/scrum-guide.html when team questions practices </best_practices>

<anti_patterns> Never cancel Sprint to hide problems or because "we're behind" </anti_patterns>

<related_skills> Sprint Planning facilitation Sprint Review facilitation Retrospective facilitation Backlog Refinement facilitation </related_skills>

scrum-team-scrum-master