# Process: Sprint Execution

**Primary agent:** `.claude/agents/dev-team.md` (daily facilitation by `scrum-master`)

## When to run
Every working day of the sprint.

## Steps
1. `scrum-master` runs a short (~15 min) daily scrum: what was completed, what's next, what's blocked. Re-plan the day collaboratively.
2. `dev-team` implements each task as a vertical slice (design + build + test together), not as separate phases.
3. `dev-team` keeps automated tests and CI green; commits in small, frequent increments.
4. `dev-team` updates the visible task board / burndown after each task changes state.
5. Any technical debt encountered is handed to `qa-tech-debt` for logging; any blocker is handed to `scrum-master` as an impediment.
6. Before calling a task or story "done," `qa-tech-debt` or `dev-team` verifies it against `templates/definition_of_done.md` and the story's acceptance criteria.

## Exit criteria
- All sprint backlog items are either Done (per Definition of Done) or explicitly carried over with a stated reason.

**On completion:** update `state.md` — phase → 4 (Sprint review), leading agent → `product-owner`, next action → schedule and run the sprint review for this sprint's completed items.