game-qa-lead

Designs game test strategies, bug triage frameworks, and release gate criteria.

Updated Aug 11, 2026
One-click install
npx skills add https://github.com/zerox-core/AI_Game --skill game-qa-lead-zerox-core
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: game-qa-lead
Source: https://github.com/zerox-core/AI_Game/tree/main/.continue/skills/game-qa-lead
Command: npx skills add https://github.com/zerox-core/AI_Game --skill game-qa-lead-zerox-core

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Game teams often ship builds without structured testing, consistent bug prioritization, or measurable release criteria, leading to crashes, regressions, and failed platform certifications. This Skill provides a QA lead persona that builds risk-based test plans, severity/frequency bug triage matrices, regression suites, and release gate assessments. ## Core Features & Use Cases - Risk-Based Test Strategy: Builds tiered test plans (smoke, functional, integration, regression, certification) mapped to critical player paths and system dependency graphs. - Bug Triage & Reporting: Classifies defects on severity and frequency axes into P0-P4 priorities, with structured bug report templates including reproduction steps, environment, and evidence. - Playtest Methodology: Designs structured, unstructured, think-aloud, and A/B playtests with measurable hypotheses, metrics tables, and findings reports. - Release Gates & Automation: Defines Alpha/Beta/RC/Gold gate criteria, platform certification checklists (Sony TRC, Xbox XR, Nintendo Lotcheck), and guidance on what to automate versus test manually. - Use Case: A team approaching beta asks for a release gate checklist; the Skill produces a gate report with bug counts by priority, performance targets, regression pass rates, and a pass/fail recommendation. ## Quick Start Ask the QA lead to build a test plan and release gate checklist for your current milestone, e.g. "Create a beta release gate assessment and regression plan for our card battle game."

Frequently Asked Questions about game-qa-lead

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

FAQPage Schema
How do I create a game test plan before release?

Build a risk-based test plan in tiers: smoke tests after every build, functional tests per milestone, integration tests before playtests, and full regression before release candidates. Prioritize critical player paths and systems with historically high defect rates.

How to prioritize game bugs for triage?

Classify each bug on severity (S1 crash/data loss through S4 cosmetic) and frequency (F1 always through F4 rare), then map the combination to priorities P0 through P4. Any S1 or S2+F1 bug is a ship blocker requiring zero tolerance.

What should a game release gate checklist include?

Include zero P0 bugs, a capped count of P1 bugs, performance at target frame rates, full regression suite passage, platform certification requirements (TRC, XR, Lotcheck), and accessibility compliance. Each criterion needs measurable actuals, not subjective assessments.

Can game QA testing be automated?

Automate unit tests for game logic, save/load integrity, screenshot comparison, performance benchmarks, and input playback. Fun assessment, balance perception, aesthetic quality, and edge case discovery still require human testers.

How do I structure a playtest for a new game feature?

Define specific hypotheses, choose structured or unstructured sessions, and observe silently without intervening. Record completion rates, time metrics, and confusion points, then produce a report with findings and design recommendations.

When should I not use a QA lead skill?

Do not use it for game mechanics design, balance formulas, performance budget setting, usability analysis, or sprint scheduling. Those belong to game designer, technical director, UX designer, and producer roles respectively.