reflect — turn this session's problems into durable improvements

Every session teaches something. This skill harvests those lessons and files each one where it will actually fire next time, so the workflow compounds.

It is problem-focused, not a summary. If you want "what did I do", that is invoice-generator. If you want one bug's canonical record, that is post-mortem. reflect asks: what should change about how we work?

When NOT to run

• Trivial or purely conversational sessions — concluding "no durable lesson" and exiting is a valid, first-class outcome. Do not manufacture findings.
• As a stand-in for invoice-generator or post-mortem.

Scope