skills.rest
claretagrapelike32
claretagrapelike32COMMUNITY
Explore all skills by this author →
GitHub

team-qa

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

Updated Aug 2, 2026
Search Tags:#testing#game development#qa#bug report#sign-off#sprint#test plan
One-click install
npx skills add https://github.com/claretagrapelike32/codex-ai-game-studio --skill team-qa-claretagrapelike32
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: team-qa
Source: https://github.com/claretagrapelike32/codex-ai-game-studio/tree/main/plugins/ai-game-studio/skills/team-qa
Command: npx skills add https://github.com/claretagrapelike32/codex-ai-game-studio --skill team-qa-claretagrapelike32

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Coordinating a full QA cycle for a game development sprint involves strategy, test planning, test case writing, manual execution, and sign-off reporting, which is error-prone when done ad hoc. This Skill automates that orchestration by delegating work to qa-lead and qa-tester subagents with gated user approvals at each phase. ## Core Features & Use Cases - QA Strategy and 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 and Test Case Generation: Produces a structured QA plan with entry/exit criteria and spawns parallel qa-tester subagents to write detailed test cases per story. - Manual QA Execution and Bug Filing: Batches stories for user-driven pass/fail decisions 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 stories, run the cycle to get a test plan, execute manual QA on visual stories, file bugs for failures, and receive a sign-off report before advancing the build. ## Quick Start Ask the assistant to run the team-qa skill for sprint-03 and walk you through the full QA cycle from strategy to sign-off.

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, generates a QA strategy and test plan, writes test cases, walks you through manual QA, and produces a sign-off report with a final verdict.

How does the skill handle a failed smoke check before QA?▼

The qa-lead checks for an existing smoke check report in production/qa/smoke-*.md during the strategy phase. If the verdict is FAIL, the cycle stops immediately and lists the failures; you must fix them, re-run the smoke check, and restart the QA cycle.

Can I run the QA cycle without director gate agents?▼

Yes. Pass a review mode argument or set production/review-mode.txt to lean or solo. Lean mode keeps only phase-gate directors, while solo mode skips all director gates and runs the pipeline without agent gates.

What happens when a story fails manual QA testing?▼

When you mark a story as FAIL, the skill collects your failure description and spawns a qa-tester subagent to write a formal bug report in production/qa/bugs/ using the BUG-NNN-slug.md naming convention, then includes it in the sign-off report.

What are the limitations of the QA sign-off verdict?▼

The verdict is APPROVED only when all stories pass with no open S1/S2 bugs; any open S1/S2 bug or undocumented failure results in NOT APPROVED. The cycle also depends on existing story files and smoke check reports, so missing inputs can block completion.

Related Skills

Explore More Software Engineering Skills→
Euraika-LabsEuraika-Labs
14

team-qa

Orchestrates end-to-end sprint QA with smoke checks, test plans, and sign-off reports.

Official
Advanced
striderZAstriderZA
72

smoke-check

Run automated smoke tests and generate a PASS/FAIL QA readiness report.

Community
Advanced
Yanick-mjYanick-mj

mb-sm

Coordinate sprint planning and backlog management with status tracking.

Community
Intermediate
XGanQAQXGanQAQ
1

team-qa

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

Community
Advanced