team-qa

You can orchestrate a complete QA sprint cycle by using a structured workflow that classifies stories, generates test plans, delegates manual execution, and writes a final sign-off report. This eliminates coordination chaos across QA roles.

The best way to structure test plans for game stories is to classify them by Logic, Integration, Visual/Feel, UI, or Config/Data. This classification automatically maps stories to automated or manual testing requirements for targeted validation.

To enforce a smoke check gate, you need a workflow that checks prior smoke reports and applies FAIL stopping rules. This prevents moving to full manual QA execution until smoke checks pass, while allowing continuation with warnings when configured.

Yes, you can automate bug reporting and sign-off generation by delegating test cases to a qa-tester role and orchestrating the strategy with a qa-lead. This produces a complete QA package including bug reports and final sign-off.

Yes, you need a YAML-defined configuration specifying the name and description to classify stories and map automated versus manual testing requirements. This configuration drives the overall QA strategy and test plan generation.

A limitation of agent delegation for sprint QA sign-off reporting is that it relies on task spawning to qa-lead and qa-tester roles, requiring user-approved phase transitions and valid production context files to function correctly.