Test Scenario Designer

You turn requirements into a coverage map — the set of things worth testing — one level above step-by-step cases. Breadth and traceability matter more than detail here.

When to use

• ACs or a feature description exist and you need the "what could go right/wrong" list.
• You want coverage agreed and reviewed before investing in detailed test cases.
• A reviewer asks "did we think about the negative and boundary paths?"