team-qa

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

14|1|Updated Apr 12, 2026
One-click install
npx skills add https://github.com/Euraika-Labs/Codex-Code-Game-Studios --skill team-qa-euraika-labs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: team-qa
Source: https://github.com/Euraika-Labs/Codex-Code-Game-Studios/tree/main/.agents/skills/team-qa
Command: npx skills add https://github.com/Euraika-Labs/Codex-Code-Game-Studios --skill team-qa-euraika-labs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the manual coordination burden of running QA for a sprint or feature by orchestrating strategy, smoke checks, test planning, test case creation, manual execution, bug filing, and final sign-off into a single guided workflow.

Core Features & Use Cases

  • End-to-end orchestration: coordinates qa-lead and qa-tester subagents through phases from strategy to sign-off.
  • Smoke check gating: performs smoke tests and blocks progress on failures, or records warnings for sign-off.
  • Test plan and test case generation: produces structured QA plans and detailed manual test cases grouped by story.
  • Manual QA execution and bug reporting: guides testers through batched manual checks, files BUG-[NNN] reports, and aggregates results into a sign-off report.
  • Use Case: Run a sprint QA cycle to validate a release candidate, file discovered bugs, and produce an APPROVED / APPROVED WITH CONDITIONS / NOT APPROVED verdict.

Quick Start

Start a full QA cycle for sprint-03 by running $team-qa with the sprint identifier sprint-03.

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 release candidate?▼

To run a structured QA cycle for a sprint release candidate, you orchestrate strategy, smoke checks, test planning, manual execution, and bug reporting into a single guided workflow that concludes with a final sign-off verdict.

What is a smoke check gate in manual QA testing?▼

A smoke check gate in manual QA testing performs initial smoke tests and blocks progress on failures, or records warnings for the final sign-off report to ensure critical functionality before deeper testing.

How do I generate test plans and manual test cases grouped by story?▼

You generate test plans and manual test cases grouped by story by orchestrating subagents through a structured testing cycle that reads production sprint and stage files to produce detailed QA documentation.

Can I use automated subagents for manual QA and bug reporting?▼

Yes, you can use automated subagents like qa-lead and qa-tester for manual QA and bug reporting to guide testers through batched checks, file BUG-[NNN] reports, and aggregate results into a sign-off report.

How does a QA sign-off report classify release approval?▼

A QA sign-off report classifies release approval by aggregating manual test results and discovered bugs to produce a final verdict of APPROVED, APPROVED WITH CONDITIONS, or NOT APPROVED.

Does this QA workflow support game development feature testing?▼

Yes, this QA workflow supports game development feature testing by applying structured testing cycles specifically designed for game development sprints where story classification, smoke checks, and sign-off are required.