gds-retrospective

Consolidate post-epic learnings and action items with ownership and status.

Updated Dec 23, 2025

Search Tags:#retrospective #agile #epic #team-collaboration #process-improvement #action-items #lessons-learned

Ready to run

npx skills add https://github.com/joekhosbayar/go-mighty --skill gds-retrospective-joekhosbayar

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: gds-retrospective
Source: https://github.com/joekhosbayar/go-mighty/tree/main/.gemini/skills/gds-retrospective
Command: npx skills add https://github.com/joekhosbayar/go-mighty --skill gds-retrospective-joekhosbayar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

After completing an epic, teams often struggle to capture lessons, track action items, and apply improvements. This skill provides a structured retrospective workflow to surface insights, document commitments, and drive continuous improvement.

Core Features & Use Cases

Structured Epic Retrospectives: guides the team through epic review, lessons learned, and next-epic planning.
Action Item Tracking: records commitments with ownership and status, enabling follow-through.
Cross-epic Learning: compares with previous retrospectives to measure progress and uptake of improvements.
Facilitator Support: provides a discussion framework to maintain psychological safety and productive dialogue.

Quick Start

Trigger the retrospective for a completed epic by saying "run retrospective for Epic <epic-number>"

Frequently Asked Questions about gds-retrospective

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I run a structured retrospective for a completed agile epic?▼

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.

What is the best way to track action items and ownership after an epic retrospective?▼

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.

How can our team compare lessons learned across multiple completed epics?▼

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.

Can I use this retrospective framework to prepare for upcoming epics?▼

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.

How does this skill support facilitators during a team retrospective?▼

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.

Do I need any specific agile tools or integrations to document post-epic learnings?▼

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.