bmad-retrospective

To conduct a post-epic review, run the bmad-retrospective skill to automate the extraction of lessons, assess outcomes, and plan for future improvements. It analyzes epic documentation and sprint status to provide comprehensive insights.

Yes, you can customize the retrospective process to align with your specific team structure and project requirements. This customization ensures the post-epic review accurately reflects your unique workflow and development process.

To run an automated post-epic retrospective, you need access to epic documentation, sprint status data, and team configurations. These inputs allow the skill to analyze the development process and identify areas for improvement.

The best way to analyze development processes and plan for the next epic is to use an automated retrospective tool that integrates with project documentation. This approach identifies areas for improvement and refines your team collaboration processes.

Yes, the retrospective skill integrates directly with project documentation and sprint status. This integration provides comprehensive insights into the completed epic and helps assess overall success.

You should not use an automated post-epic review if you lack accessible epic documentation, sprint status data, or team configurations. The skill requires these specific inputs to extract lessons and assess outcomes accurately.