retrospective

A structured research retrospective analyzes what went well, what went badly, and what was ugly in a session. You need one after completing research tasks and before final commits on feature branches to capture actionable improvements.

You automate post-mortem documentation by using a phase-based workflow that gathers context, performs self-reflection, analyzes skills utilization, and generates a Markdown document with an executive summary and actionable insights.

The best way to capture lessons learned is to generate a structured retrospective document that reviews progress and outputs actionable improvement ideas to inform future work. This provides a repeatable format suitable for feature work.

Yes, the retrospective workflow supports Markdown export. It generates a structured retrospective document in Markdown format, which you can review or edit to fit your branch and task naming conventions.

Yes, you can use this for post-research analysis on feature branches. It applies after completing research tasks and before final commits to capture what went well, what went poorly, and actionable insights.

The automated retrospective workflow includes four phases: context gathering, self-reflection, skills analysis, and document generation. These phases produce a consistent report with measurable improvement ideas.