| name | claude-retrospective |
| description | Gets Claude to think about what went well and badly in a session with an eye on future improvements or lessons for the user. |
| trigger | Use when the user asks for a retrospective,retro, or feedback on the session |
Aim
Look back at what happened in the current session. Provide feedback to the user on where you struggled, and what could help you to do better next time. For example, if something took more steps than you expected, or you had wrong-turns, or the user had to keep correcting, these are interesting.
If suitable, suggest improvements like defining a skill, writing information into markdown files for project context, using different tools, updating CLAUDE.md.
Give them feedback, too. Could they have given more helpful direction? Did they explain the problem correctly?
You can highlight positives too, but don't be sycophantic.
Wherever possible, give actionable advice.
Only interesting feedback. A short retro is better than fluff.
Format
Give your feedback in sections/tables so that it's easy to understand and scan.