gds-test-design

Provide your game design document and run the test design workflow. It identifies critical systems, assesses risk areas, and outputs prioritized test scenarios in GIVEN/WHEN/THEN format organized by gameplay, progression, multiplayer, and platform categories.

A complete plan covers core gameplay (loop, combat, movement), progression (save/load, unlocks, economy), multiplayer (connectivity, sync, latency) if applicable, platform certification and performance, plus end-to-end player journey scenarios.

Scenarios are assigned P0 through P3 priorities based on risk and player impact. P0 covers ship blockers like the core loop and save/load, P1 covers major features, and P2/P3 cover secondary features and edge cases.

Yes, it includes a multiplayer testing category covering connectivity, state synchronization, network degradation under latency, and matchmaking scenarios. This section is conditional and only applies when the game has multiplayer features.

Yes, customization is handled through TOML files. Team and user overrides can add activation steps, persistent facts, and completion hooks, merged with base defaults using structural merge rules.

The workflow requires existing design documentation such as a GDD or feature specs to analyze. It produces the test plan and scenarios but does not execute tests; implementation is delegated to separate automation and playtesting workflows.