retrospective-writer

Automated agile sprint retrospectives are generated by running retrospective-writer after sprint reviews to capture metrics, lessons, and action items. It uses a fresh-context retrospective-author to reduce bias and saves outputs to .sprints/active/retrospective-sprint-{N}.md.

Fresh-context retrospective authoring is a mechanism that uses a clean subagent context to evaluate sprint cycles without prior bias. It provides an unbiased assessment of what went well, what didn't, and lessons learned, ensuring honest documentation.

Task-cycle retrospectives are documented by running the retrospective-writer at the end of a task cycle. It saves the retrospective to .sprints/active/retrospective-task-cycle.md and appends actionable improvements to HANDOFF.md for the next cycle.

Retrospective-writer requires no external dependencies or components to function. It operates independently within your environment to generate structured retrospective templates and manage handoff documentation.

The best way to capture action items from sprint reviews is using a structured retrospective template that extracts concrete improvements. Retrospective-writer automatically appends these action items to HANDOFF.md, ensuring they are addressed in the next cycle.

You should run the retrospective generation process immediately after each sprint review and at the completion of a task cycle. This timing ensures metrics and lessons are captured accurately while the context is still relevant for handoff.