team-qa

Coordinate QA teams to generate test plans, cases, and sign-off reports.

Updated Apr 10, 2026
One-click install
npx skills add https://github.com/polsegu/Claude-Code-Game-Dev --skill team-qa-polsegu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: team-qa
Source: https://github.com/polsegu/Claude-Code-Game-Dev/tree/main/.claude/skills/team-qa
Command: npx skills add https://github.com/polsegu/Claude-Code-Game-Dev --skill team-qa-polsegu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill coordinates a QA team to remove ad-hoc, inconsistent testing by running a structured, auditable QA cycle for a sprint or feature, ensuring test plans, test cases, manual execution, bug reports, and a sign-off report are produced reliably.

Core Features & Use Cases

  • QA Strategy & Smoke Check: Spawn a qa-lead to classify stories, assess smoke tests, and produce a strategy with entry/exit criteria.
  • Test Plan & Test Case Generation: Produce a structured test plan and spawn qa-tester agents to create detailed manual test cases per story.
  • Manual Execution & Bug Filing: Guide manual QA execution with user checkpoints, collect PASS/FAIL outcomes, and auto-create BUG-[NNN] reports when failures occur.
  • Sign-Off Report & Verdicts: Aggregate results into a formal sign-off verdict (APPROVED / APPROVED WITH CONDITIONS / NOT APPROVED) and optionally write artifacts to the production QA directory.
  • Use Case: Run a complete QA pass for sprint-03 to validate feature readiness, file blocking bugs, and produce a QA sign-off document for release gating.

Quick Start

Run the team-qa skill for sprint-03 to generate a QA strategy, test plan, test cases, execute manual QA, and produce a sign-off report.

Frequently Asked Questions about team-qa

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

FAQPage Schema
How do I run a structured QA cycle for a sprint to get a release sign-off?

Generate structured test cases by spawning qa-tester agents that analyze project story files and create detailed manual test cases per story, ensuring comprehensive feature coverage and traceability.

How does manual bug reporting work during test case execution?

A QA sign-off report aggregates all test execution results into a formal verdict of APPROVED, APPROVED WITH CONDITIONS, or NOT APPROVED, optionally writing QA artifacts to the production directory.

What do I need to set up before generating a QA strategy and test plan?

Yes, this QA cycle applies to game development sprints and feature scopes, producing test plans, manual test cases, bug reports, and sign-off documents tailored to validate game feature readiness.

What is the difference between a smoke test and a full manual QA pass?

A QA sign-off report aggregates all test execution results into a formal verdict of APPROVED, APPROVED WITH CONDITIONS, or NOT APPROVED, optionally writing QA artifacts to the production directory.