retrospective

Generate a sprint retrospective by reading sprint files and git logs to compare planned tasks against actual commits. This computes completion rates, unplanned work, and carryover, producing a structured markdown retrospective ready for your repository.

Automated agile velocity analysis compares planned tasks against commit history and sprint files to compute completion rates and carryovers. It identifies velocity trends across iterations, detects TODO/FIXME growth, and checks if previous action items were addressed.

Yes, you can track recurring blockers and carryover by comparing sprint plans to git commit activity. The analysis identifies carryover tasks, detects recurring blockers, and highlights estimation accuracy to generate prioritized action items for the next iteration.

Monitor technical debt trends by analyzing git logs for TODO, FIXME, and HACK occurrences across sprints. The retrospective process identifies growth patterns in these markers to highlight accumulating technical debt in the structured markdown output.

Yes, sprint or milestone plan files are required inputs alongside git commit history. The retrospective compares these planned tasks against actual git activity to calculate completion rates, identify unplanned work, and generate actionable insights.

The best way to follow up on previous action items is to read past retrospective files and cross-reference them with current git activity. This checks whether prior action items were addressed and generates 3-5 concrete actions for the next iteration.