team-qa

End-to-end QA testing for a sprint is coordinated by orchestrating strategy, test plan generation, and execution across QA roles. This process delegates tasks to subagents to write test cases and bug reports, culminating in a consolidated sign-off report.

A complete sprint QA package includes generated test plans, written test cases, smoke checks, manual QA execution results, and final sign-off reporting. It consolidates all testing artifacts into a stakeholder-ready document.

To generate a test plan and write test cases for a new feature, you orchestrate a QA cycle from context loading to execution. A QA lead subagent handles test plan generation while a tester subagent writes the specific test cases.

Yes, you can automate the coordination of smoke checks and manual QA execution for feature releases. The workflow uses phase reviews and decision prompts to manage blockers, ensuring both automated and manual testing steps are completed.

Yes, this QA workflow requires designated QA lead and QA tester subagents to function correctly. These roles are explicitly delegated tasks such as writing test cases, generating bug reports, and performing execution checks.

The best way to manage blockers and scope during a QA cycle is through structured phase reviews and decision prompts. This approach coordinates subagents to handle scope adjustments and resolve blockers before final sign-off.