session-retro

To capture session outcomes, run a retrospective that identifies what worked, what failed, and emerging patterns. It produces a 5–10 bullet summary of actionable feedback and appends it to session-notes.md under a '## Retrospective' heading.

Logging process learning from troubleshooting involves summarizing session insights as concise bullets and writing them to session-notes.md. Generally applicable lessons can also be promoted directly into CLAUDE.md to guide future project work.

Creating a retrospective summary for team communication requires extracting what worked and what did not during your work session. The output is a brief 5–10 bullet summary appended to session-notes.md, preventing lost insights.

Yes, you can add universal insights to CLAUDE.md. After capturing session lessons, the retrospective suggests promoting generally applicable learnings into CLAUDE.md to improve future project guidance.

No, session-notes.md does not need to exist beforehand. The retrospective will create the file if it does not exist, otherwise it appends a new '## Retrospective' section to the existing notes.

You need a retrospective for product improvement after any structured discussion, planning review, or development work where outcomes and lessons must be recorded. It ensures valuable learnings become actionable improvements instead of getting lost.