skills.rest
watchthelight
watchthelightCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

gds-test-design

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

Updated Sep 3, 2026
Search Tags:#test automation#qa#test design#test scenarios#game testing#gdd#coverage matrix
One-click install
npx skills add https://github.com/watchthelight/shatterfish --skill gds-test-design-watchthelight
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gds-test-design
Source: https://github.com/watchthelight/shatterfish/tree/main/.claude/skills/gds-test-design
Command: npx skills add https://github.com/watchthelight/shatterfish --skill gds-test-design-watchthelight

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Game teams often lack a structured, risk-based test plan, leading to untested critical systems like save/load, combat, and platform certification. This Skill analyzes game design documentation and produces a complete, prioritized test design document. ## Core Features & Use Cases - Risk-Based Scenario Generation: Creates GIVEN/WHEN/THEN test scenarios across gameplay, progression, multiplayer, platform, and E2E 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. - Use Case: A QA engineer on a roguelike project asks for a test design; the Skill reads the GDD, identifies the core loop and save system as P0 risks, and outputs game-test-design.md with prioritized scenarios ready for team review. ## Quick Start Ask the assistant to design tests for the game project using the gds-test-design workflow based on the existing game design documentation.

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 game test plan from a GDD?▼

Provide your game design document and invoke the test design workflow. It identifies critical systems like the core loop and save/load, assesses risk, and outputs prioritized GIVEN/WHEN/THEN scenarios in a game-test-design.md document.

What test categories should a game QA plan cover?▼

A complete plan covers core gameplay (combat, movement, UI), progression (save/load, economy, achievements), multiplayer (connectivity, sync, latency) if applicable, platform certification and performance, and end-to-end player journeys.

How are game test scenarios prioritized?▼

Scenarios use P0-P3 priorities based on risk and player impact. P0 covers ship blockers like the core loop and save data 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 with scenarios for connectivity, state synchronization, high-latency degradation, and matchmaking, drawn from a dedicated multiplayer-testing knowledge reference.

Which game tests should be automated versus manual?▼

The workflow recommends automating P0/P1 scenarios as unit, integration, and E2E tests, while reserving manual testing for subjective areas like game feel, polish, and playtesting sessions.

Related Skills

Explore More Software Engineering Skills→
claretagrapelike32claretagrapelike32

art-bible

Authors a section-by-section art bible defining visual identity and asset standards for game production.

Community
Advanced
rudironsonirudironsoni
1

dotnet-harness-test-framework

Execute predefined .NET test cases for skill validation with reporting.

Community
Intermediate
ArchaonHWArchaonHW

gds-playtest-plan

Creates structured playtesting plans with session guides, observation templates, and analysis frameworks.

Community
Intermediate
wojonswojons
4

testing-level-poc

Define minimal manual and unit testing strategies for Proof of Concept projects.

Community
Basic