scenariolisted

# scenario > Decompose a feature across 12 risk dimensions → exhaustive, severity-tagged edge cases. ## What this is — and isn't | Skill | Does | |---|---| | `vd:test` | **Runs** tests, reports pass/fail | | `vd:brainstorm` | Explores *solution* options | | **`scenario`** | **Enumerates** edge cases & failure modes to test — does not run or fix them | Output is an input to test-writing / QA / `vd:plan` risk sections — not executable tests. ## Modes | Mode | Behaviour | |---|---| | _(default)_ | One pass over all 12 dimensions → scenario list. | | `--saturation` | Iterative rounds until coverage is exhausted (2 consecutive zero-new rounds) or `--iterations` cap (default 5). | `--iterations` only applies with `--saturation` (default mode is a single pass). ## Workflow 1. **Read the target** — the file/function or feature description. Identify inputs, outputs, state, external calls. 2. **Walk the 12 dimensions** — see [`references/dimensions.md`](references/dimensions.md). For each, ask "what input/condition in this category breaks the target?" 3. **Emit scenarios** — group by dimension; each: a one-line condition, **severity** (Critical/High/Med/Low), why it breaks, suggested test/assertion. 4. **(saturation)** — repeat with a completeness critic ("which dimension or angle is still thin?"); dedupe against the seen-set; stop per the rules in [`references/saturation-loop.md`](references/saturation-loop.md). 5. **Save** the report — write to the injected path (`.work/repo