Game Reverse Document

Generates docs from an existing game codebase as a forked report writer: reverse-engineered GDD, architecture overview with ADR drafts, concept document, or a one-page brief for new teammates and coding agents (Godot, Unity, Unreal, web). Use for "document this codebase", "generate docs from code", "onboard me to this codebase". Not for new designs (use game-gdd-author).

57 stars 6 forksWriting & Content Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add AlterLab-IEU/AlterLab_GameForge

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add AlterLab-IEU/AlterLab_GameForge --skill game-reverse-document
Manual install
git 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-reverse-document ~/.claude/skills/game-reverse-document

Personal 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 -- Reverse Documentation

Most games start with passion, not paperwork. A prototype works, then grows, and weeks later nobody,
including its author, can explain its architecture without reading every file. In 2026 add a new
twist: much of that code was written by coding agents across dozens of sessions, each of which knew
only what its prompt told it. The design lives in the code and in commit messages, nowhere else.

This workflow reads the code and writes the documents that should have existed: a design document
in the language of game design, an architecture overview in the language of systems, a concept
document that captures what the prototype is really about, or a one-page brief that lets a new
teammate (human or agent) work safely on day one. It is not an API-doc generator.

Reverse documentation serves three needs: **onboarding** (hours of reading instead of weeks of
archaeology), **preservation** (decisions captured before anyone forgets why), and **diagnosis**
(systems that disagree become visible when documented side by side).

## How this skill runs

This skill runs as a **forked subagent**: no conversation history, no questions to the user,
read access to the repository plus `git log/diff/show/status`, and permission to write new
documentation files. Therefore:

- **Never ask.** Choose the mode and scope with the rules below and list every assumption at the top
  of the document under "Assumptions and limits".
Read the full skill on GitHub

Details

Skill name
game-reverse-document
Path
skills/workflows/game-reverse-document/SKILL.md
License
MIT
Repo updated
6 November 2026

FAQ

What does the Game Reverse Document skill do?

Generates docs from an existing game codebase as a forked report writer: reverse-engineered GDD, architecture overview with ADR drafts, concept document, or a one-page brief for new teammates and coding agents (Godot, Unity, Unreal, web). Use for "document this codebase", "generate docs from code", "onboard me to this codebase". Not for new designs (use game-gdd-author).

How do I install the Game Reverse Document 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 Reverse Document 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

57

AlterLab-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).

Frontend & DesignIn 1 list

Game AI Assets

57

AlterLab-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).

AI, LLMs & AgentsIn 1 list

Game Analytics Setup

57

AlterLab-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).

Data & AnalyticsIn 1 list

Refresh Wiki

47

bholmesdev/llm-knowledge-base-skills

Regenerate wikis in the wikis/ directory. Use when asked to update, manage, or refresh the contents of the wiki from new content.

Writing & Content

Game Localization Manager

57

AlterLab-IEU/AlterLab_GameForge

Plans and runs game localization: i18n architecture, string extraction per engine, a machine translation + LLM + human review pipeline, pseudo-localization in CI, fonts, RTL and CJK, LQA, and Steam AI disclosure for translated text. Use for "localization", "translation", "i18n", "RTL", "CJK", "pseudo-localization". Not for writing dialogue (use game-narrative-director).

Writing & ContentIn 1 list

Build My Engineering Wiki

40

makenotion/cursor-notion-plugin

Build a personalized Notion engineering home from technical docs, project context, and chat or connected sources. Use to get started with an engineering wiki and a clear view of current work.

Writing & ContentIn 1 list21

Browse the most popular Claude skills, all writing & content skills, or write your own with the skills generator.