sumo-qa-executing-qa-rollout

Execute approved QA plans with isolated subagents and two-stage review gates.

5|1|Updated May 12, 2026
One-click install
npx skills add https://github.com/sumithr/sumo-qa --skill sumo-qa-executing-qa-rollout
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sumo-qa-executing-qa-rollout
Source: https://github.com/sumithr/sumo-qa/tree/main/skills/sumo-qa-executing-qa-rollout
Command: npx skills add https://github.com/sumithr/sumo-qa --skill sumo-qa-executing-qa-rollout

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

It removes the risk of shallow or incorrect test generation by executing a previously approved QA plan with isolated subagents and mandatory two-stage review before any task is considered done.

Core Features & Use Cases

  • Task-by-task subagent execution: Runs each plan task in a fresh delegated worker to prevent context pollution and ensure deterministic, scoped work.
  • Two-stage review gate per task: Enforces a spec-correctness review (risk coverage and red-phase expectations) followed by a test-quality review (observability, determinism, and tautology avoidance).
  • Continuous execution loop: Processes tasks continuously with parallel “waves” based on the plan’s parallel/sequential markers, avoiding mid-plan user check-ins.
  • Plan integrity cross-task review: Performs a final reviewer step across all task outputs to confirm collective risk coverage and absence of coverage seams.

Quick Start

Use this skill when you already have a signed QA plan and want the system to dispatch and execute each task in isolation with spec-and-quality reviews, finishing by handing off to sumo-qa-finishing-qa-work.

Frequently Asked Questions about sumo-qa-executing-qa-rollout

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate QA plan execution with isolated subagents?

Automating QA plan execution involves dispatching one fresh subagent per task to run in continuous parallel waves. This approach enforces a two-stage review gate for spec correctness and test quality before completing the work.

What is a two-stage review gate in test execution?

A two-stage review gate validates generated tests by first checking spec correctness for risk coverage and TDD red phase expectations, then verifying test quality for observability, determinism, and tautology avoidance before marking a task done.

How does subagent orchestration prevent context pollution during test generation?

Subagent orchestration prevents context pollution by delegating each QA plan task to a fresh, isolated worker. This scoped delegation ensures deterministic execution without residual context from previous tasks affecting current test generation.

Can I run mutation testing tasks in parallel waves using a QA plan?

Yes, QA plans with sequential and parallel markers allow tasks like mutation testing to execute in continuous parallel waves. The system processes these markers to dispatch tasks concurrently without requiring mid-plan user check-ins.

What happens when a test review fails during subagent execution?

When a test review fails, the system re-dispatches the task to a fresh worker with a bounded retry limit. This ensures failed tasks get repeated execution attempts until they pass both spec correctness and test quality reviews.

Do I need a signed QA plan before dispatching test execution subagents?

Yes, you need a previously approved QA plan before execution. The system requires a signed plan to dispatch isolated subagents for each task, apply review gates, and hand off to the finishing stage for final cross-task integrity checks.