soak-test

Generate a soak test protocol with a chosen duration and focus, then follow the pre-session setup checklist and record metrics at each timed checkpoint while a human plays. The skill generates the observation protocol and analysis harness; the actual playing is done by a human observer.

A soak test runs 30 minutes to several hours to surface memory leaks, performance drift, and fatigue effects that only appear after sustained play. A standard playtest is typically around 30 minutes focused on a single feature, and a smoke check covers the critical path in about 10 minutes.

In Godot 4, use the Debugger Monitors tab to track Static Memory and Object Count. In Unity, use the Memory Profiler to record Total Reserved and GC Allocated memory. In Unreal, use the stat memory console command to track Physical Memory Used at each checkpoint.

Duration should match the game's session design: 30 minutes for a single mechanic, 1 hour for standard coverage, 2 hours for a first full Polish soak, and 4 hours for games with long session design like RPGs or sims.

No. The skill explicitly generates a protocol for human execution because the observations, including fun fatigue and content exhaustion judgments, require a human observer. It never attempts to run the soak automatically.