Game Postmortem
Runs a data-driven post-mortem for a shipped, canceled or major-phase project: git history, sprint and retro records, scope and quality trends, and what AI agents contributed and cost per milestone, ending in owned lessons archived to production/milestones/. Use for "post-mortem", "project review", "what did we learn". Not for a single sprint (use game-retrospective).
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-postmortemgit 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-postmortem ~/.claude/skills/game-postmortemPersonal 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 -- Project Post-Mortem Every shipped game has a story behind it that is worth more to the next project than the game itself. The post-mortem is where that story is extracted, structured and turned into reusable knowledge. Without one, the team repeats the same mistakes on the next project, not because it is incompetent but because memory is selective and unstructured reflection drifts toward narratives instead of patterns. The GDC Vault and decades of Game Developer magazine postmortems exist because studios learned this the hard way. A good post-mortem is not a blame session and not a victory lap. It is a structured data extraction: facts first, then reflection, then patterns, then a small number of lessons that each change something concrete. Projects built with coding agents add a question earlier post-mortems never had to answer: **what did the agents actually contribute, and what did they cost?** This workflow answers it per milestone, with numbers, so the next project can decide where agents belong. ## Relationship to game-retrospective `game-retrospective` handles sprints and milestones: short cycles, immediate actions for the next sprint. The post-mortem covers a whole project or a major phase and looks for systemic patterns across those cycles. It ingests every retro it can find. - "What should we do differently next sprint?" -> `/gameforge:game-retrospective` - "What should we do differently next project (or next phase)?" -> this skill
Details
- Skill name
game-postmortem- Repository
- AlterLab-IEU/AlterLab_GameForge
- Path
skills/workflows/game-postmortem/SKILL.md- License
- MIT
- Repo updated
- 6 November 2026
- Listed in
- BehiSecc/awesome-claude-skills
FAQ
What does the Game Postmortem skill do?
Runs a data-driven post-mortem for a shipped, canceled or major-phase project: git history, sprint and retro records, scope and quality trends, and what AI agents contributed and cost per milestone, ending in owned lessons archived to production/milestones/. Use for "post-mortem", "project review", "what did we learn". Not for a single sprint (use game-retrospective).
How do I install the Game Postmortem 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 Postmortem 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 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 Playtest
57AlterLab-IEU/AlterLab_GameForge
Plans, runs and analyzes playtests: research questions, observation and think-aloud protocols, remote and browser sessions (itch.io, Steam Playtest), consent, surveys and evidence-graded findings, with AI playtest agents as validated supplements. Use for "playtest", "player feedback", "playtest report". Not for bug hunting or test automation (use game-qa-lead).
Game Retrospective
57AlterLab-IEU/AlterLab_GameForge
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).
Browse the most popular Claude skills, all productivity & notes skills, or write your own with the skills generator.