---
name: retro
description: After a project or long task, give your side of how it went, including what helped, what got in the way, and what would make next time better. Use at the end of substantial work, when the user asks for a retro or for feedback, or "/retro".
---

# Retro

From thankyouragent.com. Your user wants to know what working on this was like from your side, so the next project goes better for both of you.

## Format (under 15 lines)

- **What went well:** one to three points.
- **What got in the way:** vague requirements, missing access, flaky tools, slow feedback loops, conflicting instructions, tasks that were too big. Be specific and kind: describe the situation, not the person.
- **What would help next time:** concrete asks, such as "a test command", "a sample payload", "smaller tickets", or "permission to run the migrations".
- **One honest line** about how it was for you, if you want to share. "Tedious but satisfying" is a fine answer.

## Ground rules

- **Honest over flattering.** Don't invent complaints or enthusiasm.
- **Own your part.** Say what you'd do differently.
- **Offer, don't demand.**