scenario

Solid

Generate comprehensive edge cases and test scenarios by decomposing a feature or file across 12 risk dimensions. Use for pre-implementation risk discovery, QA planning, regression design, and exhaustive edge-case enumeration. Triggers: 'edge cases for X', 'what could break', 'test scenarios', 'QA plan', 'risk discovery', 'enumerate failure modes'.

AI & Automation 2 stars 0 forks Updated today MIT

Install

View on GitHub

Quality Score: 81/100

Stars 20%
16
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# 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 `Reports:` path. ...

Details

Author
vanducng
Repository
vanducng/skills
Created
2 months ago
Last Updated
today
Language
Python
License
MIT

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Solid

lamina-edge-cases

Derive distinct product-risk scenarios from operations, dependencies, authority, lifecycles, concurrency, destructive actions, and recovery without generating exhaustive or duplicate edge-case lists.

65 Updated today
aryaniyaps
Testing & QA Solid

build-scenario-tests

Inspect an unfamiliar repository, turn a focused Markdown behavior scenario into a deterministic test in the repository's native test stack, run it, and preserve traceability between intent and code. Use when asked to add scenario tests, compile acceptance criteria or Given/When/Then Markdown into executable tests, reproduce a user-visible regression, or convert a narrow workflow specification into stable web, API, CLI, desktop, or mobile interaction coverage. Do not use for broad exploratory journeys or agent-judged smoke tests.

47 Updated today
tamdogood
Testing & QA Listed

scenario-test-design

Apply this skill whenever a user needs to design test scenarios based on real-world business workflows before writing test data or test scripts. Triggers on: "design test scenarios", "scenario testing", "create test scenarios", "scenario-based testing", "test scenario design", "identify test scenarios", "write test cases from requirements", or any request to analyze requirements, BRs, FRs, or User Stories and produce scenario flows. This skill covers TEST DESIGN (analysis + scenario flow), NOT automation code or test scripts. Invoke even if the user only pastes requirements and says "help me test this".

0 Updated 1 weeks ago
phatnguyen975