retro

To generate a structured retrospective from a work session, you need a tool that identifies critical decisions, waste, and learning from session logs. This process produces a retro.md file alongside plan.md and lessons.md to capture actionable insights and drive continuous improvement.

Documenting critical decisions and waste reduction from team sprints requires applying post-session reflection to session logs. This generates an structured retro report that captures insights and actionable improvements for future planning meetings and code reviews.

Yes, you can apply deep expert analysis to session analysis by enabling the --deep mode. This exposes an optional expert lens framework that provides advanced insights and structured knowledge capture beyond the default light retrospective report.

Yes, the retrospective process works for code reviews and planning meetings. It applies post-session reflection and knowledge capture to these contexts, identifying critical decisions and generating structured documentation for continuous improvement.

Creating a retrospective report produces a primary retro.md file alongside related plan.md and lessons.md artifacts. These documents structure the extracted insights, waste reduction strategies, and actionable improvements from your session analysis.

You need a structured retro instead of informal post-session notes to effectively drive continuous improvement across teams. Structured documentation ensures critical decisions, waste, and learning are consistently captured and transformed into actionable improvements.