Negative Scenario Discovery

Discover failure, denial, degradation, and unsafe-recovery paths from goals, input constraints, permissions, dependency contracts, timeout/retry, idempotency/transaction, and recovery design. Produce NS-##. Do not write full test cases, run fault injection, invent error codes, or declare behavior correct.

When to Use

• Use it to examine invalid input, unauthorized access, dependency failure, timeout, retry exhaustion, duplicate request, partial failure, and inconsistency.
• Use it to find failure stimuli and observable outcomes outside the happy path from designs or past failures.
• Use it when failure contracts are incomplete and evidence gaps, recovery choices, and Human decisions must be explicit.

Do not use it only to find boundary values, write full cases, run fault injection, conduct a real incident review, or choose final copy/SLA for a team.

Output Format Options

• Use Markdown by default; when a table, CSV, or JSON is requested, preserve the same evidence, status, impact, owner, and validation fields.
• Do not present a structured format or static inventory as execution, pass, approval, or release evidence.

How to Use