Game GMT Review

Overview

Use this skill to review a game design proposal through GMT: Goal, Means, Tools. Treat GMT as an analysis framework, not a rigid pass/fail doctrine. Identify whether the proposal distinguishes player goals, experience goals, and design goals; whether each goal is supported by suitable means and concrete tools; and where the design has gaps, contradictions, weak links, or unproven assumptions.

Read references/gmt-framework.md before performing a substantive review. Use references/review-output.md when the user asks for a formal report, review memo, scoring table, or actionable recommendations.

Review Workflow

1. Extract the proposal's stated and implied goals.

   • Separate player goals, experience goals, and design goals.
   • Mark goals as stated, inferred, missing, or ambiguous.
   • Do not force the three goal types to align automatically; note whether their relationship is intentional, weak, absent, or contradictory.

2. Build the GMT map.

   • For player GMT, map player goals to high-level means such as strategy, tactics, operation, exploration, resource management, traversal, social cooperation, puzzle solving, collection, optimization, survival, or creation.
   • For experience GMT, map experience goals to means such as interaction, sensory presentation, narrative, worldbuilding, theme, structure, aesthetic tone, genre convention, pacing, and content organization.
   • For each means, list concrete tools: rules, controls, 3C, level design, AI, abilities, feedback, UI, economy, enemies, missions, art, animation, audio, story beats, production assets, and progression systems.