game-postmortem
From the author
Run a structured post-mortem analyzing what went well, what went wrong, and extractable lessons. Pulls git history, milestone data, and retrospective notes automatically. Triggers on: "post-mortem", "project review", "what did we learn", "lessons learned", or when a major milestone or project is complete. Do NOT invoke for sprint-level retrospectives (use game-retrospective) or design reviews (use game-design-review). Part of the AlterLab GameForge collection.
Install
npx skills add AlterLab-IEU/AlterLab_GameForge --skill game-postmortem -a claude-code
Installs to .claude/skills/game-postmortem/ · Each command fetches the skill straight from GitHub with the open skills CLI.
Byte-identical to the scanned commit, with the repository’s licence and a SOURCE.txt.
Want your agent to suggest skills while you type? See how to use skills from your IDE.
Safety checks on SKILL.md
No warnings.
Why 74
aiqbench computes the trust score from public signals. It is not a security audit, so read a skill before you install it.
Similar skills
Closest to this one by what they do and when they are used.
- game-retrospectiveAlterLab-IEU/AlterLab_GameForgeRun a game development post-mortem rooted in the GDC tradition. Triggers on: "retrospective", "retro", "post-mortem", "lessons learned", "what went right", "what went wrong", "kill list review". Do NOT invoke for design document review (use game-design-review) or playtesting (use game-playtest). Part of the AlterLab GameForge collection.Design★ 50
- after-action-reportrampstackco/claude-skillsRun a structured after-action review (postmortem, retrospective) on a launch, incident, or completed project to capture timeline, root cause analysis, contributing factors, and actionable lessons. Use this skill whenever the user wants to run a postmortem, retrospective, AAR, or after-action review on any past event. Triggers on after-action report, AAR, postmortem, retrospective, retro, post-incident review, what went well what didn't, lessons learned, blameless postmortem, root cause analysis, RCA, five whys. Also triggers when the user has just shipped something or just resolved an incident and wants to capture learnings.Engineering★ 1K
- post-mortemalirezarezvani/claude-skills/c-level-agents:post-mortem [decision] — Honest retrospective on an executed decision, scored against original assumptions and dissent. Closes the strategic sprint loop. Use when a decision hits its 90-day review checkpoint or its kill criteria trigger — e.g. scoring last quarter's pricing change against its pre-committed success metrics.Engineering★ 29K
- retrophuryn/pm-skillsFacilitate a structured sprint retrospective — what went well, what didn't, and prioritized action items with owners and deadlines. Use when running a retrospective, reflecting on a sprint, creating action items from team feedback, or learning how to run effective retros.Other★ 27.5K
- game-design-reviewYuki001/game-dev-skillsReview, critique, compare, improve, or stress-test an existing game concept, GDD, mechanic, puzzle, economy, level, theme, emotional arc, interface, narrative, social feature, prototype, pitch, or playtest result. Use when the user asks what is weak, risky, unclear, unbalanced, contradictory, insufficiently engaging, or worth validating next in a game design. Produce evidence-based findings, explicit tradeoffs, and the smallest useful prototype or playtest experiment.Design★ 105
- incident-postmortemgithub/awesome-copilotUse when an outage, production incident, or significant service degradation has occurred and the team needs to write a structured blameless post-mortem. Triggers on phrases like "write a post-mortem", "incident review", "what went wrong", "outage report", "root cause analysis", or "RCA". Covers timeline reconstruction, contributing factor analysis, impact quantification, and action item generation with owners.Writing★ 40.6K
Ratings & reviews
—
no reviews
Tried this skill? Rate it to help others. Sign in
Discussion
Join the discussion. Sign in