create-retro

Generate a sprint retrospective by providing the sprint name and period to produce a Start/Stop/Continue structure with assigned owners, due dates, and verification steps. This automates the retrospective workflow and outputs a shareable document for team alignment.

Yes, you can audit past retrospectives to extract action items and check their completion status. This process surfaces recurring themes and unresolved issues from previous sprints, helping your team close the loop on continuous improvement and avoid repeating mistakes.

The Start/Stop/Continue format is an agile retrospective framework that identifies new behaviors to begin, ineffective practices to end, and successful processes to maintain. It structures team feedback into actionable guidance with clear accountability to improve sprint velocity.

Ensure action items are completed by assigning clear owners, specific due dates, and verification steps to each task generated in the retrospective. The workflow reads past retros to audit completion status, holding the team accountable and closing the loop on unresolved actions.

Yes, this retrospective generation process applies to project seasons and broader team cycles, not just standard sprints. It reviews previous actions, surfaces recurring themes, and produces structured Start/Stop/Continue guidance for any defined period of team work.

The best way to share a retrospective document is to generate it with structured actions, themes, and accountability, then save the output directly to your project docs. This provides a centralized, shareable record for product, engineering, and design teams to align on improvements.