speckit-retro-run

Automate retrospective analysis by gathering cycle artifacts like spec.md, tasks.md, plan.md, and QA reports to compute git metrics and compare specs to implementation. This generates a comprehensive retrospective report containing actionable insights for future iterations.

A spec-driven retrospective evaluates a completed development cycle by comparing initial specifications to the final implementation. You need this structured process when you want to capture cycle metrics, document learnings, and generate concrete process-improvement suggestions.

Generate metrics and improvement suggestions by synthesizing development artifacts and computing git metrics across specification, planning, implementation, QA, and release activities. This holistic view produces a retrospective report with trends and concrete improvements for next iterations.

Yes, you can use retrospective metrics to update a project constitution. The structured retrospective analysis supports constitution updates and knowledge capture, applying optional extension hooks to automate parts of the workflow for future iterations.

Yes, the retrospective analysis works without external dependencies. It independently gathers artifacts, computes git metrics, and compares specs to implementation to generate a retrospective report, relying solely on your existing spec-driven workflow data.