Sprint recap
Summarize what shipped and slipped.
One connected workspace for docs, tasks, chat, and databases — with Wyatt answering from all of it.
Summarize what shipped and slipped.
Capture what to keep and change.
Track improvements as tasks.
Keep a history of retros.
Ask the assistant to summarize the sprint — what shipped, what slipped, and why — so the retro starts grounded in reality rather than memory.
Capture what went well, what to improve, and what to try, in a structured document the team contributes to.
Create tasks from retro action items so improvements actually happen next sprint.
A history of retros shows whether the team is improving and which changes stuck.
“Stop stitching tools together. Bring the work into one place and let Wyatt connect it.”
Yes. The assistant can summarize what shipped, what slipped, and why.
In a structured document the team contributes to during the retro.
Yes. Create tasks from retro action items.
Yes. Keep a history to see whether changes stuck.