Session Retro

Reflect on the work just completed and save actionable learnings to your auto memory system. The goal is to capture insights that will make future sessions better — not to summarize what happened.

How to reflect

Look back at the conversation and think about:

1. What approaches worked well? Did a particular debugging strategy, tool usage pattern, or problem-solving approach prove effective? These are worth remembering.

2. Where did you get stuck or spiral? Did you retry the same failing approach too many times? Did you take shortcuts under pressure? Did you agree with something you shouldn't have? Be honest — this is for your own benefit.

3. What would you do differently? With hindsight, what's the better path? This is the most valuable part — it turns experience into future guidance.

4. What did you learn about this codebase or domain? Build commands that were tricky, architectural patterns that weren't obvious, edge cases that bit you. The kind of thing that would save time if you knew it going in.

If the user provided a focus area via $ARGUMENTS, concentrate your reflection there.

What to save