bmad-retrospective

A project retrospective after completing an epic is facilitated by reading and executing a predefined workflow that captures user input and provides a structured review process to summarize work and discuss lessons learned.

The best way to document lessons learned during a project review is to use a structured retrospective workflow that captures user input, identifies major issues, and records what went well and what could be improved for future reference.

Yes, this retrospective process applies to software development workflows and general project management. It helps review completed work, address major issues, and plan the next epic based on past experiences.

To plan the next epic based on past project experiences, you conduct a structured end-of-epic review to capture lessons learned, discuss major issues, and use those insights to set the stage for the next project.

An end-of-epic work review should include a summary of completed work, a discussion of what went well, identification of areas for improvement, documentation of lessons learned, and addressing major issues encountered during the epic.

No specific dependencies are required to run this retrospective workflow. The Skill operates independently using predefined scripts to capture user input and facilitate the structured review process.