sumo-qa-planning-qa-rollout

To turn a QA objective into a rollout plan, you convert the amorphous request into a written, dispatchable plan with bite-sized tasks and anchored file/risk coverage. This produces a single plan artifact ready for subagent execution before any test code is written.

The best way to break down a large QA story is to split the work into 3 to 10 independent chunks sized for short execution windows. Each chunk receives explicit task approach tagging and per-task deliverable definitions for clear handoff.

To structure test execution plans to match repository conventions, you walk the repository to identify real files touched, test framework fixture patterns, and CI configurations. This ensures task placement and risk coverage align with existing practice.

The QA planning process generates only the planning artifact, satisfying a planner-only requirement. It produces a markdown document at docs/qa/plans/ with stepwise confirmation gates and explicit task approach tagging without writing any test code.

You should not use automated QA planning when your PR or strategy phase work cannot be split into at least 3 independently executable chunks. It is designed specifically for scenarios requiring preparation before any test code is written.