team-qa

Orchestrates QA lead and tester subagents through a full sprint testing cycle.

13|Updated Jul 30, 2026
One-click install
npx skills add https://github.com/frabcd/codex-ai-game-studio --skill team-qa-frabcd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: team-qa
Source: https://github.com/frabcd/codex-ai-game-studio/tree/main/plugins/ai-game-studio/skills/team-qa
Command: npx skills add https://github.com/frabcd/codex-ai-game-studio --skill team-qa-frabcd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Coordinating a complete QA cycle for a game development sprint—strategy, test planning, test case writing, manual execution, bug reporting, and sign-off—normally requires juggling multiple roles and documents. This Skill automates that orchestration by delegating work to qa-lead and qa-tester subagents with user approval gates at every phase. ## Core Features & Use Cases - QA Strategy & Smoke Check Gate: Classifies stories by type (Logic, Integration, Visual/Feel, UI, Config/Data), checks existing smoke check reports, and blocks the cycle on a FAIL verdict. - Test Plan & Test Case Generation: Produces a structured QA plan with entry/exit criteria, then spawns qa-tester subagents in parallel to write detailed test cases per story. - Manual QA Execution & Bug Filing: Batches stories for user-driven pass/fail review and automatically writes formal bug reports (BUG-NNN) for failures. - Sign-Off Report: Generates an APPROVED / APPROVED WITH CONDITIONS / NOT APPROVED verdict with coverage tables and next-step guidance. - Use Case: After finishing sprint-03 of your game project, invoke this Skill to run the full QA cycle: it reads the sprint stories, verifies the smoke check, writes the test plan, walks you through manual QA, files bugs, and produces a sign-off report. ## Quick Start Ask Codex to run the team-qa skill for sprint-03 and orchestrate the full QA cycle with strategy, test cases, and 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 full QA cycle for a game development sprint?

Invoke the team-qa skill with a sprint identifier like sprint-03. It loads the sprint stories, runs a QA strategy phase with smoke check verification, generates a test plan, writes test cases, walks you through manual QA, and produces a sign-off report.

What happens if the smoke check fails before QA testing?

The cycle stops at the strategy phase. The qa-lead lists the smoke check failures, and you must fix the issues, re-run the smoke-check skill, and then re-run team-qa before proceeding to test planning.

Can I run the QA cycle without director gate approvals?

Yes. Pass a review mode argument or set production/review-mode.txt to lean or solo. Lean mode skips director gates except phase-gate types, while solo mode skips all director gate spawning entirely.

How are bugs documented when a story fails manual QA?

After you report a FAIL result, a qa-tester subagent writes a formal bug report in production/qa/bugs/ using the naming convention BUG-NNN-short-slug.md, incrementing the number from existing bug files.

What determines the final QA sign-off verdict?

APPROVED requires all stories passing with no open S1/S2 bugs. APPROVED WITH CONDITIONS allows open S3/S4 bugs or documented notes. NOT APPROVED results from any open S1/S2 bugs or undocumented failures.