team-qa

Coordinate QA strategy, test planning, manual execution, and sign-off verdicts.

1|Updated May 5, 2026
One-click install
npx skills add https://github.com/XGanQAQ/Unity-Claude-Code-Game-Studios --skill team-qa-xganqaq
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: team-qa
Source: https://github.com/XGanQAQ/Unity-Claude-Code-Game-Studios/tree/main/.claude/skills/team-qa
Command: npx skills add https://github.com/XGanQAQ/Unity-Claude-Code-Game-Studios --skill team-qa-xganqaq

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

team-qa eliminates the risk of shipping defects by coordinating a full QA cycle with clear strategy, repeatable test plans, manual verification, and a final sign-off report.

Core Features & Use Cases

  • QA strategy and smoke check gate: Produces a sprint/feature-focused QA strategy and blocks progression on smoke check failures.
  • Test plan + structured test cases: Writes a formal QA plan and generates story-scoped manual test cases for review.
  • Manual execution + bug reporting: Conducts walkthrough-based manual QA, records outcomes, and files formal bugs when failures occur.
  • Sign-off with verdict rules: Generates a coverage summary and issues an APPROVED / APPROVED WITH CONDITIONS / NOT APPROVED verdict with next-step guidance.

Quick Start

Run /team-qa with argument "sprint-03" to orchestrate QA strategy, test planning, manual QA (where needed), and sign-off for the stories in that sprint.

Frequently Asked Questions about team-qa

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

FAQPage Schema
How do I run end-to-end QA testing for a sprint or feature release?▼

Manual QA execution involves conducting walkthrough-based testing of story-scoped test cases, recording outcomes, and filing formal bug reports when failures occur during the sprint verification cycle.

What is a smoke check gate in sprint QA strategy?▼

Release readiness sign-off computes a coverage summary and issues an APPROVED, APPROVED WITH CONDITIONS, or NOT APPROVED verdict based on manual QA outcomes, providing next-step guidance for the sprint.

How do I generate structured test cases from production story directories?▼

To start sprint QA orchestration, run the command with the sprint identifier as an argument, which triggers phase transitions requiring AskUserQuestion-driven approvals between strategy, planning, and execution phases.

Can I use agent orchestration for manual test planning and bug reporting?▼

Using agent orchestration for QA requires AskUserQuestion-driven approvals at phase transitions and tool-based Task delegation to qa-lead and qa-tester components to coordinate strategy, manual test execution, and bug reporting.

What is the best way to coordinate QA strategy and tester execution for release readiness?▼

Orchestrating QA strategy and tester execution requires tool-based Task delegation to qa-lead and qa-tester components, ensuring repeatable test plans, manual verification, and final sign-off verdict computation for release readiness.