What problem does it solve? Game balance changes in the kami-kakushi incremental RPG must be proven with simulation data rather than eyeballed, and this Skill encodes the full methodology: running the persona-bot sim, regenerating the committed pacing report, attributing unexplained report drift, and routing RED band violations to a human decision instead of fudging tests. ## Core Features & Use Cases - ADR-132 commit protocol: Runs verify:balance, regenerates docs/content/t0-pacing.md, and embeds a --summary block in the commit body so every magnitude change ships with its measured before/after. - Signed-band enforcement: Reads human-signed pacing constants from balance.ts, treats any RED band as a human decision fork, and explains the ADR-187 skip-blindness tradeoff of the greedy persona. - Worktree attribution proof: Regenerates the pacing report from a past SHA in a throwaway git worktree to prove which change moved unexplained t0-pacing.md rows. - Use Case: A designer asks whether a new cooking mechanic is too slow; you sim both worlds, find the rung wall-time exceeds the signed band by 6.6 minutes, and file an HD-item with the measured numbers instead of shipping or silently tuning. ## Quick Start Ask the assistant to run the balance simulation and check whether the current pacing report is fresh before proposing any change to a game balance value.
