team-qa

To coordinate a QA cycle for a sprint release, this Skill orchestrates test plan generation, parallel test case authoring, manual execution, bug reporting, and final sign-off. It classifies stories, runs smoke checks, and manages subagents to produce an auditable validation pipeline.

Generating test plans and managing manual test runs is handled by a structured pipeline that defines entry/exit criteria and guides manual execution. It captures PASS, FAIL, or BLOCKED outcomes and auto-generates formal bug reports based on acceptance-driven test cases.

Parallel test case authoring works by launching qa-tester subagents to write detailed, acceptance-driven test cases per story simultaneously. This orchestration allows multiple stories to be processed in parallel, producing comprehensive manual test coverage efficiently.

Using this QA orchestration approach requires existing repository story files and production sprint metadata. The pipeline operates against these inputs to discover stories and evaluate smoke tests, so missing inputs will trigger graceful error recovery or block recommendations.

When a smoke test fails during QA sign-off preparation, the Skill spawns a qa-lead to evaluate the results and produce a strategy with block or skip recommendations. It enforces user-approved decision points to determine whether to proceed with manual testing.

Blocked subagents and missing inputs are handled through graceful error recovery within the QA pipeline. The system captures BLOCKED outcomes during manual runs and requires AskUserQuestion approvals to resolve gating issues, ensuring the final sign-off report reflects accurate verdict rules.