gds-retrospective

Facilitate structured retrospectives for completed game development epics.

26|23|Updated Dec 16, 2025
One-click install
npx skills add https://github.com/laraxot/laravelpizza.com --skill gds-retrospective-laraxot
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gds-retrospective
Source: https://github.com/laraxot/laravelpizza.com/tree/main/.github/skills/gds-retrospective
Command: npx skills add https://github.com/laraxot/laravelpizza.com --skill gds-retrospective-laraxot

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires python, yaml, textblob, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill unit provides a structured framework to facilitate and conduct a comprehensive retrospective after completing a game development epic. It addresses the challenge of post-epic review and helps extract lessons and assess success in a collaborative manner.

Core Features & Use Cases

  • Retrospective Facilitation: Guides a Scrum Master in leading a team retrospective discussion.
  • Data Analysis: Extracts and analyzes completed epic story records to identify common struggles, review feedback patterns, and lessons learned.
  • Continuous Improvement: Assesses the application of previous retrospective action items, process improvements, and technical debt status.
  • Future Planning: Provides insights into upcoming epic dependencies and preparation needed.
  • Use Case: A Scrum Master uses this Skill unit to review the completion of a game development epic, analyze its performance, and discuss lessons learned with the development team.

Quick Start

Run a retrospective for the completed epic using the 'gds-retrospective' skill.

Frequently Asked Questions about gds-retrospective

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

FAQPage Schema
How do I facilitate a game development epic retrospective?

Facilitate a game development epic retrospective by automating the extraction of lessons and success assessments from epic story records. The tool guides Scrum Masters through a structured team collaboration discussion to review completed epics.

What is an epic retrospective in game development?

An epic retrospective in game development is a post-epic review process that extracts lessons, assesses success, and evaluates previous action items. It helps development teams collaboratively identify process improvements and technical debt status after completing an epic.

How do I analyze epic story records for lessons learned?

Analyze epic story records for lessons learned by processing YAML data and text to identify common struggles and feedback patterns. The analysis reviews completed epic performance to extract actionable insights for continuous improvement.

Do I need Python to run an automated retrospective on YAML epic data?

Yes, you need Python to run an automated retrospective on YAML epic data. The process requires Python along with the YAML and textblob libraries to parse story records and perform text analysis for feedback pattern extraction.

Can I assess previous process improvements during a team retrospective?

You can assess previous process improvements during a team retrospective by reviewing the application of past action items and technical debt status. The framework evaluates continuous learning progress and identifies future epic dependencies.

What's the best way to review technical debt status after a game development epic?

The best way to review technical debt status after a game development epic is through a structured retrospective that assesses previous action items and process improvements. This approach extracts lessons from story records while planning for upcoming epic dependencies.