team-qa

Coordinate QA subagents for strategy, test case generation, and bug reporting.

Updated Apr 15, 2026
One-click install
npx skills add https://github.com/sumilee-pcu/game2026 --skill team-qa-sumilee-pcu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: team-qa
Source: https://github.com/sumilee-pcu/game2026/tree/main/.claude/skills/team-qa
Command: npx skills add https://github.com/sumilee-pcu/game2026 --skill team-qa-sumilee-pcu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the challenge of fragmented testing processes by providing a structured, automated framework for managing QA teams, ensuring that game features are thoroughly tested and verified before release.

Core Features & Use Cases

  • Automated QA Orchestration: Coordinates specialized subagents (qa-lead and qa-tester) to handle strategy, test planning, and bug reporting.
  • Structured Testing Pipeline: Implements a rigorous multi-phase cycle including smoke checks, manual test case execution, and formal sign-off.
  • Use Case: Use this during a sprint to automatically generate a test plan, identify blockers, and track bug reports for new game mechanics, ensuring the build is stable before moving to the next development phase.

Quick Start

Invoke the team-qa skill with the argument sprint-03 to begin the full testing cycle for the third sprint.

Frequently Asked Questions about team-qa

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

FAQPage Schema
How do I automate QA testing workflows for game development sprints?

Automated QA testing for game development sprints is orchestrated by coordinating specialized subagents that handle test strategy, test case generation, and structured bug tracking. This framework executes multi-phase cycles including smoke checks and manual test execution to verify new game mechanics before release.

What is the best way to structure bug tracking and smoke testing for new game features?

The best way to structure bug tracking and smoke testing for game features is through a unified multi-phase QA pipeline. This workflow generates a formal test plan, identifies blockers, executes manual test cases, and issues a formal sign-off to ensure build stability before moving to the next development phase.

Can I use an automated QA workflow to generate test plans and identify blockers during a sprint?

Yes, you can use an automated QA workflow to generate test plans and identify blockers during a sprint. By invoking the workflow with a sprint identifier, it coordinates specialized subagents to strategize, execute manual test cases, and track bug reports for new game mechanics automatically.

Does game development QA orchestration require any external dependencies or components?

Game development QA orchestration operates without external dependencies or components. It uses an advanced internal design that coordinates specialized subagents natively to manage the testing strategy, test case generation, and bug reporting cycle within a self-contained automated workflow.

When do I need an end-to-end QA cycle with formal sign-off for a game release?

An end-to-end QA cycle with formal sign-off is needed during game development sprints and feature releases requiring rigorous validation. It ensures new game mechanics pass smoke checks and manual test execution, providing structured bug tracking to verify the build is stable before moving forward.