gds-retrospective

To run an agile epic retrospective, trigger the workflow by requesting a retrospective for a specific epic number. The skill guides your team through epic review, lessons learned, and next-epic planning using structured discussion prompts.

Tracking action items after an epic retrospective requires recording commitments with designated ownership and status. This skill captures those action items to ensure follow-through and drive continuous process improvement across the team.

Comparing lessons learned across multiple completed epics involves aligning current retrospective insights with previous ones. This skill consolidates cross-epic learnings to measure progress and verify the uptake of past process improvements.

Yes, you can use this retrospective framework to prepare for upcoming epics. It applies to agile development teams conducting post-epic reviews while simultaneously planning improvements for the next development cycle.

This skill supports facilitators during a team retrospective by providing a structured discussion framework. It helps maintain psychological safety and productive dialogue while guiding the team through the review process.

No specific agile tool integrations are needed to document post-epic learnings. The skill operates independently to consolidate insights, record action items, and align cross-epic learnings without requiring external dependencies.