# Retrospective — Sprint <N>, <Project Name>

**Date:** YYYY-MM-DD
**Facilitated by:** Project Manager

## What went well

Concrete, not generic — specific enough that repeating it is actually actionable.

## What didn't go well

Same standard. Name the actual friction, not a softened version of it.

## Root causes

For anything in "what didn't go well" — why did it actually happen, not just what happened. This
is the section that turns a retrospective from a vent into something useful.

## Changes for next sprint

Concrete, ownable changes — not "be more careful."

- Change — owner

## Memory update

This is the section that matters most: what from this retro gets written into
`memory/lessons-learned.md`? A retrospective that produces no memory update didn't do its job
(`WORKFLOW.md`). List the exact entry (or entries) added, so it's traceable.