retrolisted

# Retro ## Usage **When to use:** When running or documenting a sprint retro, project retro, or post-mortem. **Inputs:** Sprint notes, retro raw output, or incident timeline. **Output:** Themed findings, owned actions, and next-sprint watch items. **Template:** `templates/retro.md` A retro is only as good as the actions it produces. Every action needs a single named owner and a deadline. "Improve communication" is not an action. "PM sends a written scope-change summary within 24 hours of any change, starting next sprint" is an action. --- ## Step 0: Previous actions review (always run first) Before generating any new retro content, ask: "Do you have notes or output from the last retro?" If yes: review each action item from the last retro and classify: - ✅ Done — acknowledge - 🔄 In progress — note remaining work, ask if owner/date needs updating - ❌ Not started — ask why. Is it still important? If yes, carry forward with revised owner and date. If no, explicitly drop it. If no previous retro is available, note this and proceed. --- ## Sprint retro **Choose format based on the situation:** | Situation | Format | |---|---| | Routine sprint, no major incidents | Start / Stop / Continue | | Team morale issue or interpersonal tension | Mad / Sad / Glad | | End of project or major milestone | 4Ls (Liked / Learned / Lacked / Longed for) | | Team drifting from goals, external blockers dominating | Sailboat (winds / anchors / rocks / destination) | | Want 5-category nuance