Analyzes game balance data files, formulas, and configuration to identify outliers, broken progressions, degenerate strategies, and economy imbalances. Use after modifying any balance-related data or design. Use when user says 'balance report', 'check game balance', 'run a balance check'.
Determine the balance domain from $ARGUMENTS[0]:
If no argument, ask the user which system to check.
Read relevant files from assets/data/ and design/balance/ for the identified domain.
Note every file read — they will appear in the Data Sources section of the report.
Read the GDD for the system from to understand intended design targets, tuning knobs, and expected value ranges. This is the baseline for "correct" behaviour.
design/gdd/Run domain-specific checks:
Combat balance:
Economy balance:
Progression balance:
Loot balance:
## Balance Check: [System Name]
### Data Sources Analyzed
- [List of files read]
### Health Summary: [HEALTHY / CONCERNS / CRITICAL ISSUES]
### Outliers Detected
| Item/Value | Expected Range | Actual | Issue |
|-----------|---------------|--------|-------|
### Degenerate Strategies Found
- [Strategy description and why it is problematic]
### Progression Analysis
[Graph description or table showing progression curve health]
### Recommendations
| Priority | Issue | Suggested Fix | Impact |
|----------|-------|--------------|--------|
### Values That Need Attention
[Specific values with suggested adjustments and rationale]
After presenting the report, ask:
"Would you like to fix any of these balance issues now?"
If yes:
assets/data/ or formula in design/balance/"This value is defined in a design document. Run
/propagate-design-change [path]on the affected GDD to find downstream impacts before committing."
If no:
design/balance/balance-check-[system]-[date].md for laterEnd with:
"Re-run
/balance-checkafter fixes to verify."