balance-check

## Phase 1: Identify Balance Domain Determine the balance domain from `$ARGUMENTS`: - **Combat** → weapon/ability DPS, time-to-kill, damage type interactions - **Economy** → resource faucets/sinks, acquisition rates, item pricing - **Progression** → XP/power curves, dead zones, power spikes - **Loot** → rarity distribution, pity timers, inventory pressure - **File path given** → load that file directly and infer domain from content If no argument, use `question`: - "Which system should I check for balance?" - Options: `[A] Combat balance` / `[B] Economy balance` / `[C] Progression balance` / `[D] Loot balance` --- ## Phase 2: Gather Context Run these in parallel using Glob/Grep: ``` Glob pattern="assets/data/**/*.json" → find all data files Glob pattern="assets/data/**/*.tres" → find Godot resource data files Grep pattern="balance" path="design/gdd/" → find relevant GDDs Glob pattern="design/balance/**/*.md" → find previous balance reports ``` - Read the GDD for the identified domain from `design/gdd/` - Read all relevant data files from `assets/data/` - Extract intended design targets, tuning knobs, and expected value ranges from the GDD --- ## Phase 3: Delegate Expert Analysis Spawn specialist agents via Task in **parallel** for the identified domain. Pass the full GDD content and data file content to each agent. ### Combat balance → spawn `systems-designer` Ask them to: - Calculate DPS for all weapons/abilities at each power tier - Check time-to-kill at each ti...