Game Design KPI Coverage Audit

Check whether the evaluation framework is seeing the whole value of the feature, or only the parts that are easy to measure.

Use this skill when a feature is being judged mainly through directly attributable KPIs and you suspect that measurement logic is biasing the team toward flashy, self-contained systems while undervaluing connective tissue, UX, quality-of-life, enabling systems, or long-term structural work.

Read references/value-types.md when identifying what kind of value the feature creates. Read references/blind-spot-patterns.md when diagnosing common KPI-coverage failures. Read references/recommendation-patterns.md when deciding how to justify or evaluate hard-to-measure work.

What to produce

Produce:

1. Feature read - what the proposal is and what role it plays
2. Current KPI framing - what the team is measuring or expecting to measure
3. Coverage diagnosis - what value is covered versus ignored by those KPIs
4. Blind spots - what may be neglected because it is hard to measure directly
5. Risk of mis-prioritization - what bad decisions may result from the current framing
6. Evaluation recommendation - how the feature should be justified, monitored, or compared more fairly