gds-test-design

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

6|Updated Aug 29, 2026
One-click install
npx skills add https://github.com/HordRicJr/Akomagni --skill gds-test-design-hordricjr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gds-test-design
Source: https://github.com/HordRicJr/Akomagni/tree/main/bmad-core/.agents/skills/gds-test-design
Command: npx skills add https://github.com/HordRicJr/Akomagni --skill gds-test-design-hordricjr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Game teams often lack a structured, risk-based test plan, leaving critical gameplay, save, multiplayer, and platform certification issues undiscovered until late in development. ## Core Features & Use Cases - Risk-Based Test Scenarios: Generates GIVEN/WHEN/THEN scenarios across gameplay, progression, multiplayer, platform, and E2E categories with P0-P3 priorities. - Coverage Matrix & Automation Strategy: Produces a feature-by-priority coverage matrix plus recommendations on what to automate versus test manually. - Structured Deliverable: Outputs a complete game-test-design.md document using a template, validated against a checklist. - Use Case: After finishing a GDD for a turn-based strategy game, run this workflow to produce a prioritized test plan covering combat, save/load roundtrips, and certification requirements before writing any test code. ## Quick Start Ask the agent to design tests for your game project based on the existing game design document.

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 GIVEN/WHEN/THEN test scenarios across gameplay, progression, multiplayer, and platform categories, output as a game-test-design.md file.

What test categories should a game QA plan cover?

A complete game test design covers core gameplay (combat, movement, UI), progression (save/load, unlocks, economy), multiplayer (connectivity, sync, latency), platform certification (TRC/XR, input, performance), and E2E player journeys.

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 with scenarios for connectivity, state synchronization, high-latency degradation, and matchmaking, applied only when the game design documentation indicates 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 certification requirements, and an understanding of the core gameplay loop before it can generate scenarios.