Post-Analysis: Retrospective

To generate a data-driven project retrospective from Git logs, you can use an automated analysis tool that parses commit history and progress JSON files to identify development bottlenecks. It processes this data to produce a structured Markdown report highlighting error patterns and areas for improvement.

A post-mortem analysis in software development is a retrospective process that evaluates project performance after completion. It works by aggregating progress data and parsing Git logs to pinpoint phases with high iteration counts, error concentrations, and repeated file modifications to suggest actionable improvements.

Yes, you can analyze project bottlenecks using progress JSON files like `.claude-full-auto-progress.json`. By leveraging this progress data alongside Git logs, the analysis identifies specific development phases that were time-consuming and files that required the most revisions.

You can identify error patterns and repeated file modifications by running a retrospective analysis on your project's Git logs and progress data. This process pinpoints error concentrations and highlights which specific files required the most revisions during the development lifecycle.

This retrospective analysis tool operates independently without requiring any external dependencies. It utilizes internal scripts for Git log parsing and progress data aggregation, requiring only your project's JSON progress file and Git history to generate the structured Markdown output.

The best way to automate project retrospective reporting is by using a tool that analyzes Git logs and progress JSON files to automatically generate structured Markdown reports. This approach provides objective insights into project performance by identifying bottlenecks and suggesting actionable improvements without manual data entry.