skills.rest
PastaSus
PastaSusCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

gds-test-design

Creates prioritized game test scenarios and coverage matrices from game design documentation.

1|Updated Sep 18, 2026
Search Tags:#game development#qa#risk assessment#test design#test scenarios#game testing#coverage matrix
One-click install
npx skills add https://github.com/PastaSus/egg-defender --skill gds-test-design-pastasus
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gds-test-design
Source: https://github.com/PastaSus/egg-defender/tree/main/.agents/skills/gds-test-design
Command: npx skills add https://github.com/PastaSus/egg-defender --skill gds-test-design-pastasus

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Game teams often lack a structured, risk-based test plan, leading to missed critical bugs in core gameplay, save systems, and platform certification. This Skill turns game design documentation into a complete, prioritized test design document. ## Core Features & Use Cases - Risk-Based Test Scenarios: Generates GIVEN/WHEN/THEN scenarios across gameplay, progression, multiplayer, and platform categories with P0-P3 priorities. - Coverage Matrix & Automation Strategy: Produces a feature-vs-priority coverage matrix plus recommendations on what to automate versus test manually. - E2E Journey Testing: Defines end-to-end player journey scenarios with timeouts and infrastructure requirements. - Use Case: After finishing a GDD for a turn-based strategy game, run this workflow to produce game-test-design.md covering combat, save/load round trips, and certification requirements before writing any test code. ## Quick Start Ask the agent to design tests for my game project based on the game design document in this repo.

Frequently Asked Questions about gds-test-design

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a test plan for a video game?▼

Provide your game design document and this workflow analyzes core mechanics, assesses risk areas, and generates prioritized test scenarios in GIVEN/WHEN/THEN format. The output is a game-test-design.md file with a coverage matrix and automation strategy.

What test categories should game QA cover?▼

Game test design should cover core gameplay (combat, movement, UI), progression (save/load, economy, achievements), multiplayer (connectivity, synchronization, latency), and platform requirements (certification, input, performance, accessibility).

How are game test scenarios prioritized?▼

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

Does this workflow support multiplayer game testing?▼

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

What inputs are required before designing game tests?▼

The workflow requires game design documentation such as a GDD or feature specs, knowledge of target platforms, and an understanding of the core gameplay loop. Missing documentation limits the risk assessment and scenario coverage.

Related Skills

Explore More Software Engineering Skills→
hiktan44hiktan44

Game Designer

Designs game systems and documents them as Game Design Documents.

Community
Advanced
matiaspakuamatiaspakua

test-master

Plan and automate unit, integration, and E2E testing strategies for CI/CD.

Community
Advanced
Arete-ConsortiumArete-Consortium
4

gameplay-tester

Playtests games and produces structured bug reports, balance assessments, and UX feedback.

Official
Intermediate
TheArchitectitTheArchitectit
3

game-dev

Structure game development workflows for Unity, Godot, Unreal, and custom engines.

Community
Intermediate