Game Retrospective
Runs a sprint or milestone retrospective in the GDC post-mortem tradition: What Went Right, What Went Wrong, seven lenses including AI-assisted development, the Kill List and The One Thing, with actions fed into the next sprint. Use for "retro", "sprint retrospective", "milestone review", "kill list". Not for a whole-project post-mortem (use game-postmortem).
Install
/plugin marketplace add AlterLab-IEU/AlterLab_GameForgeThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add AlterLab-IEU/AlterLab_GameForge --skill game-retrospectivegit clone --depth 1 https://github.com/AlterLab-IEU/AlterLab_GameForge.git /tmp/AlterLab_GameForge
mkdir -p ~/.claude/skills
cp -r /tmp/AlterLab_GameForge/skills/workflows/game-retrospective ~/.claude/skills/game-retrospectivePersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# AlterLab GameForge -- Sprint and Milestone Retrospective Game development has the best post-mortem tradition in software. Game Developer magazine's long-running Postmortem column (reprinted on Gamasutra) covered games such as *Thief: The Dark Project*, *Baldur's Gate* and *Diablo II* in the same blunt shape: what went right, what went wrong. No spin, no "learnings and opportunities". This workflow brings that format down to the sprint and milestone, where the lessons are still cheap to act on. It is not an agile ceremony. A corporate retro asks "what could we improve?" A game retro asks "did we build the right game, and did we build it the right way?" One optimizes process; the other interrogates the creative and technical decisions that decide whether the game is worth shipping. In 2026 it also asks a third question: **what did the coding agents actually do for us, and what did they cost?** Teams that cannot answer that with numbers end up either over-trusting agents or abandoning them on a hunch. ## When to Use / When Not To Run it when a sprint ends, when a milestone lands (vertical slice, alpha, beta), after a pivot or a big scope cut, when the game is "fine but not fun" and nobody can say why, or when development feels stuck. | Instead of this skill... | Use | |---|---| | Whole-project or canceled-project post-mortem | `/gameforge:game-postmortem` | | Planning the next sprint from these actions | `/gameforge:game-sprint-plan` |
Details
- Skill name
game-retrospective- Repository
- AlterLab-IEU/AlterLab_GameForge
- Path
skills/workflows/game-retrospective/SKILL.md- License
- MIT
- Repo updated
- 6 November 2026
- Listed in
- BehiSecc/awesome-claude-skills
FAQ
What does the Game Retrospective skill do?
Runs a sprint or milestone retrospective in the GDC post-mortem tradition: What Went Right, What Went Wrong, seven lenses including AI-assisted development, the Kill List and The One Thing, with actions fed into the next sprint. Use for "retro", "sprint retrospective", "milestone review", "kill list". Not for a whole-project post-mortem (use game-postmortem).
How do I install the Game Retrospective skill?
Claude Code plugin: /plugin marketplace add AlterLab-IEU/AlterLab_GameForge. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Game Retrospective popular?
It lives in AlterLab-IEU/AlterLab_GameForge, which has 57 GitHub stars and 6 forks, and is included in 1 curated skill list.
Related skills
Game Accessibility Specialist
57AlterLab-IEU/AlterLab_GameForge
Accessibility Specialist (Kael Oduya). Designs motor, visual, auditory and cognitive accommodations, runs accessibility audits, scopes the European Accessibility Act, CVAA and Game Accessibility Guidelines, and maps fixes to Godot, Unity, Unreal or web. Use for "accessibility audit", "EAA", "colorblind", "subtitles", "remapping". Not for general UX flows (use game-ux-designer).
Game AI Assets
57AlterLab-IEU/AlterLab_GameForge
Runs an AI-assisted asset pipeline for models, sprites, textures, audio and voice: generate vs make vs buy, license-first tool choice, style lock, engine post-processing, and a per-asset provenance log for Steam, itch.io and EU AI Act disclosures. Use for "generate a sprite with AI", "ElevenLabs", "can I ship this AI asset". Not for defining art style (use game-art-director).
Game Analytics Setup
57AlterLab-IEU/AlterLab_GameForge
Sets up privacy-first game analytics: question-driven event taxonomies, consent-gated telemetry (GDPR, COPPA, ATT), engine and web SDK choice, KPI definitions, dashboards, A/B tests, and AI feedback summaries validated against real data. Use for "analytics", "telemetry", "KPIs", "retention", "funnel", "A/B test". Not for balance tuning (use game-balance-check).
Game Scope Check
57AlterLab-IEU/AlterLab_GameForge
Checks scope against time and capacity: feature inventory, MoSCoW with effort caps, impact and risk scores, buffer math, scope-creep signals and a cut list, with velocity calibrated for AI-agent work and vibe debt counted as risk. Use for "scope creep", "can we fit this", "what should we cut", "are we on track". Not for sprint task planning (use game-sprint-plan).
Game Prototype
57AlterLab-IEU/AlterLab_GameForge
Runs hypothesis-driven prototyping: one question per prototype, a falsifiable hypothesis, the cheapest fidelity that answers it (paper, simulation, agent-built throwaway), a time box, observed playtests and a kill-or-promote call. Use for "prototype", "proof of concept", "test this mechanic", "is this fun". Not for building a small shippable game (use game-vibe-code).
Game Sprint Plan
57AlterLab-IEU/AlterLab_GameForge
Builds a sprint plan for a team or solo developer: one pillar-aligned goal, day-sized tasks that each end in a check, dependencies, capacity with buffer, AI-agent estimates with review budgets and vibe-debt paydown, written to production/sprints/. Not for whole-project scope (use game-scope-check).
Browse the most popular Claude skills, all productivity & notes skills, or write your own with the skills generator.