team-qa

Orchestrate game QA cycles with test planning, execution, and sign-off reports.

Updated Jul 22, 2025
One-click install
npx skills add https://github.com/MichaelSolati/mkai --skill team-qa-michaelsolati
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: team-qa
Source: https://github.com/MichaelSolati/mkai/tree/main/profiles/game-dev/skills/team-qa
Command: npx skills add https://github.com/MichaelSolati/mkai --skill team-qa-michaelsolati

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the disjointed, manual effort of coordinating game QA cycles, replacing scattered spreadsheets and ad-hoc check-ins with a structured, end-to-end testing workflow that ensures no test steps or sign-offs are missed.

Core Features & Use Cases

  • Structured QA Cycle Orchestration: Coordinates specialized QA lead and QA tester subagents to handle strategy, test planning, test case writing, manual execution, and formal sign-off for game sprints or features.
  • Built-in Validation & Blocker Handling: Includes smoke check verification, blocker recovery protocols, and automatic bug report generation to keep QA workflows on track even when issues arise.
  • Use Case: A game studio preparing a new feature sprint can use this Skill to automatically generate a full QA package including test plans, test cases, and a formal sign-off report, without manually coordinating QA leads and testers or tracking results in disconnected tools.

Quick Start

Invoke the team-qa skill with your current sprint or feature identifier to automatically generate a full QA strategy, test plan, and sign-off report for all in-scope game features.

Frequently Asked Questions about team-qa

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

FAQPage Schema
How do I automate game QA test planning and bug reporting for a new sprint?

Automate game QA test planning by orchestrating specialized subagents to handle test case writing, manual execution, and bug reporting. This generates a full QA package including test plans and sign-off reports for sprint deliverables.

What is the best way to structure end-to-end quality assurance for game features?

Structured end-to-end quality assurance for game features coordinates QA lead and tester subagents to execute test plans, perform smoke checks, and handle blockers. This replaces scattered spreadsheets with a repeatable, auditable QA workflow.

How do I handle blocker recovery and smoke check validation during game testing?

Handle blocker recovery and smoke check validation during game testing by using built-in protocols that generate automatic bug reports. These protocols keep QA workflows on track and ensure build quality even when issues arise.

Can I generate a formal QA sign-off report for game development sprints automatically?

Generate a formal QA sign-off report for game development sprints automatically by invoking an orchestration skill with your sprint identifier. It coordinates the entire testing cycle to produce the final sign-off documentation.

Does structured QA cycle orchestration support manual test case execution for games?

Structured QA cycle orchestration supports manual test case execution for games by coordinating specialized tester subagents. These agents execute the written test cases and report results to ensure no test steps are missed.

When do I need a coordinated QA workflow instead of ad-hoc testing for game development?

You need a coordinated QA workflow instead of ad-hoc testing when preparing a new feature sprint that requires auditable, repeatable processes. It ensures formal smoke check validation and blocker recovery before build release.