Turn a change description into a short, prioritized test plan.
Process
- Restate what changed in one sentence.
- Identify the riskiest behaviors first (data loss, auth, money, concurrency).
- List concrete test cases as
given / when / then, happy paths first, then edge cases and failure modes. - Note any setup, fixtures, or environment the cases need.
- Call out what is explicitly out of scope so the plan stays focused.
Output format
## Risks
- Ranked list of the riskiest areas.
Cases
- given … / when … / then …
Out of scope
- Anything intentionally not covered.
Keep the plan small enough to act on immediately. If the change is unclear, ask
for the acceptance criteria before listing cases.