game-improvement-analysis

Analyze a game's codebase and produce a prioritized, actionable improvement report — concrete problems, ideas, and changes — ranked by player-experience priorities (default Fun > Feel > Performance > Challenge > Consistency, but honor any order the user states). Fan the analysis out across those dimensions with parallel subagents (or a Workflow if available), then synthesize one ranked report. Use this whenever the user wants to improve, review, critique, audit, or "make more fun" a game / prototype / level, asks "what should I build or fix next" for a game, or wants a read on game feel, balance, juice, or progression — even if they don't say the word "analyze". This is read-only analysis; offer to implement the picks afterward, don't change code as part of the analysis.