Agent skill

Test Scenarios

Generate test scenario coverage from a feature spec — happy paths, edge cases, error handling, accessibility, security, and performance — with a coverage analyzer that flags gaps.

MITAuto-check passedTesting & QA

Install Test Scenarios

skills CLI

$ npx skills add borghei/Claude-Skills --skill test-scenarios -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install borghei/Claude-Skills test-scenarios --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/project-management/execution/test-scenarios .claude/skills/test-scenarios && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "test-scenarios" agent skill from https://github.com/borghei/Claude-Skills/tree/main/project-management/execution/test-scenarios into .claude/skills/test-scenarios/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "test-scenarios", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/borghei/Claude-Skills/tree/main/project-management/execution/test-scenarios

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add borghei/Claude-Skills --skill test-scenarios -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install borghei/Claude-Skills test-scenarios --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/project-management/execution/test-scenarios .agents/skills/test-scenarios && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "test-scenarios" agent skill from https://github.com/borghei/Claude-Skills/tree/main/project-management/execution/test-scenarios into .agents/skills/test-scenarios/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "test-scenarios", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add borghei/Claude-Skills --skill test-scenarios -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install borghei/Claude-Skills test-scenarios --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/project-management/execution/test-scenarios .cursor/skills/test-scenarios && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "test-scenarios" agent skill from https://github.com/borghei/Claude-Skills/tree/main/project-management/execution/test-scenarios into .cursor/skills/test-scenarios/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "test-scenarios", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/borghei/Claude-Skills.git --path project-management/execution/test-scenarios

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add borghei/Claude-Skills --skill test-scenarios -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install borghei/Claude-Skills test-scenarios --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/project-management/execution/test-scenarios .gemini/skills/test-scenarios && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "test-scenarios" agent skill from https://github.com/borghei/Claude-Skills/tree/main/project-management/execution/test-scenarios into .gemini/skills/test-scenarios/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "test-scenarios", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install borghei/Claude-Skills test-scenarios

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add borghei/Claude-Skills --skill test-scenarios -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/project-management/execution/test-scenarios .github/skills/test-scenarios && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "test-scenarios" agent skill from https://github.com/borghei/Claude-Skills/tree/main/project-management/execution/test-scenarios into .github/skills/test-scenarios/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "test-scenarios", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add borghei/Claude-Skills --skill test-scenarios -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install borghei/Claude-Skills test-scenarios --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/project-management/execution/test-scenarios .opencode/skills/test-scenarios && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "test-scenarios" agent skill from https://github.com/borghei/Claude-Skills/tree/main/project-management/execution/test-scenarios into .opencode/skills/test-scenarios/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "test-scenarios", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: test-scenarios
GitHub stars: 886
Token cost: ~1.9k tokens
SKILL.md length: 891 words
Files: 5 (incl. scripts, references, assets)
Skills in repo: 354
Repo updated: Oct 7, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Generate test scenario coverage from a feature spec — happy paths, edge cases, error handling, accessibility, security, and performance — with a coverage analyzer that flags gaps.

Works in 9 steps: Spec read → Happy path → Edge cases → …
Define what to test before QA writes the test plan
SKILL.md covers When to use this skill, The 7 scenario categories, Clarify First and Workflow, plus 5 more sections
Runs Python scripts from its folder; calls python3

What it does

Test Scenarios is an agent skill from borghei/Claude-Skills. Generate test scenario coverage from a feature spec — happy paths, edge cases, error handling, accessibility, security, and performance — with a coverage analyzer that flags gaps. Use to define what to test before QA writes the test plan.

Its SKILL.md is about 1.9k tokens, which your agent loads only when the skill is triggered. The skill folder holds 7 other files, including scripts, reference files and assets (for example `assets/scenario_template.md`, `references/coverage-anti-patterns.md` and `references/scenario-categories.md`).

It sits in Testing & QA, covering Test generation, PRD writing and Accessibility. The repository describes itself as: 385 AI skills, 77 expert agents, and 900 stdlib Python tools for every team: engineering, PM, marketing, C-level, compliance, business ops, research, and a LinkedIn toolkit… The licence is MIT.

When your agent uses it

Define what to test before QA writes the test plan
Tasks that involve Test generation
Tasks that involve PRD writing

Example prompts

“/test-scenarios”

Requirements

Python 3

Workflow steps

9 steps, taken from the step headings in SKILL.md.

Spec read
Happy path
Edge cases
Error handling
Empty / first-use / after-action states
Concurrent / race scenarios
Accessibility
Security + privacy
Run test_scenario_generator.py

What it can do on your machine

Read from SKILL.md and the folder at commit 4a698e8. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 1 file in scripts/ (Python), which the agent can run.
Shell commands in SKILL.md call:
- python3
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Test Scenarios loads about 1.9k tokens when it runs, and up to ~5.4k if it reads all its reference files. Until then it costs about 63 tokens; SKILL.md has 891 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~63
When it runs · the whole SKILL.md, loaded when a task matches: ~1.9k
With references · SKILL.md plus every file in references/, read only if the agent opens them: ~5.4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from borghei/Claude-Skills at commit 4a698e8, republished under its MIT licence (© borghei). 891 words, ~1,930 tokens.

Download SKILL.mdSave it as .claude/skills/test-scenarios/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.

name: test-scenarios
description: Generate test scenario coverage from a feature spec — happy paths, edge cases, error handling, accessibility, security, and performance — with a coverage analyzer that flags gaps. Use to define what to test before QA writes the test plan.
license: MIT + Commons Clause
metadata.version: 1.0.0
metadata.author: borghei
metadata.category: project-management
metadata.domain: execution
metadata.updated: 2026-05-27
metadata.python-tools: test_scenario_generator.py
metadata.tech-stack: test-scenarios, qa, edge-cases, acceptance-criteria

Test Scenarios

Generate complete scenario coverage from a feature spec before tests are written. Closes the gap between "we built it" and "it survives production."

When to use this skill

After PRD approval but before engineering implementation
During sprint planning to size testing effort
During code review to verify test coverage
During QA planning to scope test pass
During bug-bash prep
After a production incident to validate scenario gaps

The 7 scenario categories

For every feature, generate scenarios across:

Happy paths — primary user goals achieved cleanly
Edge cases — boundary conditions, unusual inputs
Error handling — what users see when things go wrong
Empty states — first-use, no data, after-delete
Concurrent operations — race conditions, optimistic locking
Accessibility — keyboard nav, screen reader, contrast, motion
Security + privacy — auth, permissions, PII, injection

Plus when applicable:

Performance scenarios (load, latency, throughput)
Localization (RTL, long-string, currency, date format)
Cross-platform (browsers, devices, OS versions)

Clarify First

Before generating scenarios, confirm these inputs. If any is unknown or vague, ASK — do not assume:

Feature type — form, browse/list, real-time/collab, file upload, payment, or bulk operation (drives the scenario count per category in the coverage rubric)
Risk / sensitivity profile — auth, payment, or PII involved (scales up security and concurrency coverage in the risk-weighted selection)
The spec's inputs, outputs, and side effects — what users provide, expect, and what changes in the system (drives edge cases in Step 3 and error handling in Step 4)

Stop rule: ask only the 2-3 that most change the output. If the user says "just draft it," proceed and list your assumptions at the top of the artifact.

Workflow

Step 1 — Spec read

Read the PRD / user story / acceptance criteria. Identify:

User goals (what they want to do)
Inputs (what they provide)
Outputs (what they expect)
Side effects (what changes in the system)

Step 2 — Happy path

For each user goal, write the primary flow:

Preconditions
Steps
Expected result

Aim for 1-3 happy paths per feature.

Step 3 — Edge cases

For each input, ask:

What's the empty value?
What's the minimum?
What's the maximum?
What's just below min / just above max?
What's the wrong type?
What's the weird-but-valid (very long, special chars, Unicode, emoji)?

Step 4 — Error handling

For each failure mode:

Network failure
Server error (5xx)
Validation error (4xx)
Timeout
Concurrent modification
Auth expired / lost

For each: what does the user see? Recover-from / try-again UX?

Step 5 — Empty / first-use / after-action states

First use (no data)
After delete (last item)
After error (partial state)
After timeout
After cancel

Step 6 — Concurrent / race scenarios

Two users simultaneously:

Editing same record
Triggering same action
Submitting same form
Reaching capacity limit

Step 7 — Accessibility

Tab through with keyboard
Use with screen reader
High contrast / inverted colors
Reduced motion preference
Large text scaling
Voice control

Step 8 — Security + privacy

Logged out user accesses
Unauthorized user accesses
Permission downgrade mid-action
PII handling
Injection attempts (XSS, SQLi)
Rate limiting

Step 9 — Run `test_scenario_generator.py`

Audit a candidate scenario list for category coverage; flag gaps.

bash

python3 project-management/execution/test-scenarios/scripts/test_scenario_generator.py \
  --input feature_spec.json --format markdown

Decision frameworks

Show full SKILL.md (393 more words)Show less

How many scenarios per category?

Feature type	Happy	Edge	Error	Empty	Concur	A11y	Security
Form / submission	1-3	4-8	4-6	2	1-2	4	3-5
Browse / list	2-3	3-5	2-3	2-3	1	3	2
Real-time / collab	3	4-6	4-6	2	4-6 (essential)	3	3
File upload	2	6-10 (sizes/types)	4-6	1	1-2	2	5+ (file abuse)
Payment / financial	3	6-10	8+ (critical)	2	4-6 (idempotency!)	3	8+
Bulk operation	2	4-6 (sizes)	4-6	1	2-4 (partial fail)	2	3

Adjust for risk profile of the specific feature.

Risk-weighted scenario selection

Not all scenarios need full QA coverage. Apply:

Happy path: always test
Edge cases: test those that matter (likelihood × severity)
Error handling: test all paths that user can recover from
Empty state: always test (first impression!)
Concurrent: test for data-integrity-critical features
Accessibility: baseline coverage on all UI; full coverage on user-facing
Security: scale with sensitivity (full coverage on auth/payment)

Manual vs automated

Scenario type	Default
Happy path	Automated (E2E or integration)
Edge cases (input validation)	Unit tests
Error handling	Mix (mocked errors in unit; real in integration)
Empty state	Visual regression + manual
Concurrent	Hard — usually manual + targeted integration
Accessibility	Automated (axe-core) + manual screen-reader
Security	SAST + DAST + manual review for critical paths
Performance	Automated load tests
Localization	Pseudo-localization + manual spot-check

Common engagements

"Generate test scenarios for this new feature"

Read the PRD / spec.
Apply the 7 categories.
Generate scenarios; estimate count per category.
Run validator; address gaps.
Hand to QA for implementation.

"Audit our test plan for completeness"

Categorize existing scenarios.
Identify under-covered categories.
Score by risk × likelihood.
Recommend additions.

"Post-incident scenario gap analysis"

Pull the incident scenario.
Map: which category was missed?
Add scenario; verify regression coverage.
Update default-coverage rubric for that feature type.

Anti-patterns to avoid

Only happy paths. Production fails on edges; you skipped them.
No empty state. First-use is broken.
"QA will figure it out." No, QA tests what's specified.
Generic acceptance criteria. "Should work" is not testable.
No accessibility scenarios. Excludes users; fails compliance.
No security scenarios. Vulnerable paths ship.
No performance scenarios for performance-sensitive features. Surprise at scale.
Skipping concurrent for collaborative features. Race conditions ship.

References

references/scenario-categories.md — deep on the 7+ categories with examples
references/coverage-anti-patterns.md — common gaps + fixes

project-management/execution/create-prd — upstream spec
project-management/execution/wwas — acceptance criteria
engineering/senior-qa — implementation
engineering/code-reviewer — review coverage
product-team/spec-to-repo — translating spec to tickets

Files

SKILL.md and 4 other files (scripts, references, assets) in project-management/execution/test-scenarios of borghei/Claude-Skills.

SKILL.md
assets/scenario_template.md
references/coverage-anti-patterns.md
references/scenario-categories.md
scripts/test_scenario_generator.py

Open the folder on GitHubat commit 4a698e8

Compare with similar skills

Test Scenarios next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Test Scenarios compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Test Scenarios this skillborghei/Claude-Skills	886	—	~1.9k	Automated safety check: Pass	MIT	yesterday
Corgispec QA UIricoyudog/Coding_Corgi_flow	104	—	~1.5k	Automated safety check: Pass	MIT	1 mo ago
Test Specgustavscirulis/snapgrid	117	1 repos	~12k	Automated safety check: Notes	Custom licence	5 mo ago
AI Test Generationpetrkindlmann/qa-skills	168	—	~4.8k	Automated safety check: Pass	MIT	4 mo ago
Test Strategynurettincoban/ai-prd-workflow	298	—	~1.4k	Automated safety check: Pass	MIT	today
Foreman Web TestingVisionForge-OU/foreman	443	—	~953	Automated safety check: Pass	Custom licence	3 mo ago

Similar skills

Corgispec QA UI
ricoyudog/Coding_Corgi_flow
UI walkthrough — real user path verification with screenshots, component state checks, keyboard navigation, and cross-browser testing
104 GitHub stars~1.5k tokensUpdated 1 mo ago
Testing & QAAuto-check passed
Test Spec
gustavscirulis/snapgrid
Generates comprehensive test specification with unit tests, UI tests, accessibility testing, and beta testing plan.
117 GitHub starsUsed in 1 repo~12k tokens
Testing & QAAuto-check: notes
AI Test Generation
petrkindlmann/qa-skills
Use AI to write NEW test code from specs, PRDs, user stories, code diffs, bug reports, or OpenAPI specs.
168 GitHub stars~4.8k tokensUpdated 4 mo ago
Testing & QAAuto-check passed
Test Strategy
nurettincoban/ai-prd-workflow
Write TEST-STRATEGY.md, a test plan per RFC, before the tests are written.
298 GitHub stars~1.4k tokensUpdated today
Testing & QAAuto-check passed
Foreman Web Testing
VisionForge-OU/foreman
Headless end-to-end / web-app testing for the Foreman e2e stage.
443 GitHub stars~953 tokensUpdated 3 mo ago
Testing & QAAuto-check passed
Prd V07 Test Planning
mattgierhart/PRD-driven-context-engineering
Define test cases BEFORE implementation, ensuring every API, business rule, and user journey has verifiable acceptance criteria during PRD v0.7 Build Execution.
180 GitHub stars~3.5k tokensUpdated 1 mo ago
Testing & QAAuto-check: notes

Questions about Test Scenarios

What does Test Scenarios do?

Generate test scenario coverage from a feature spec — happy paths, edge cases, error handling, accessibility, security, and performance — with a coverage analyzer that flags gaps. Test Scenarios is an agent skill from borghei/Claude-Skills. Generate test scenario coverage from a feature spec — happy paths, edge cases, error handling, accessibility, security, and performance — with a coverage analyzer that flags gaps.

When should I use Test Scenarios?

Test Scenarios fits situations like: define what to test before QA writes the test plan; tasks that involve Test generation; tasks that involve PRD writing.

How do I install Test Scenarios in Claude Code?

Run `npx skills add borghei/Claude-Skills --skill test-scenarios -a claude-code`. Or copy the skill folder (project-management/execution/test-scenarios in borghei/Claude-Skills) into .claude/skills/test-scenarios in your project. Claude Code loads it when a task matches its description.

How do I install Test Scenarios in Codex?

Run `npx skills add borghei/Claude-Skills --skill test-scenarios -a codex`. Or copy the skill folder (project-management/execution/test-scenarios in borghei/Claude-Skills) into .agents/skills/test-scenarios in your project. Codex loads it when a task matches its description.

Can I use Test Scenarios in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add borghei/Claude-Skills --skill test-scenarios -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/test-scenarios, .gemini/skills/test-scenarios, .github/skills/test-scenarios and .opencode/skills/test-scenarios in your project.

What does Test Scenarios need to run?

Going by SKILL.md and its folder, Test Scenarios needs Python for the scripts in its folder and the command-line tools its instructions call (python3). Our summary lists: Python 3.

Does Test Scenarios access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Test Scenarios safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Test Scenarios use?

Test Scenarios is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Test Scenarios use?

About 1.9k tokens (SKILL.md is roughly 7.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 3.5k tokens, read only when the agent opens those files.

What are the alternatives to Test Scenarios?

Skills that share tags, products or a category with Test Scenarios: Corgispec QA UI (ricoyudog/Coding_Corgi_flow, 104 stars), Test Spec (gustavscirulis/snapgrid, 117 stars), AI Test Generation (petrkindlmann/qa-skills, 168 stars) and Test Strategy (nurettincoban/ai-prd-workflow, 298 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Test Scenarios?

borghei (a GitHub user) maintains it in borghei/Claude-Skills, which has 886 GitHub stars. The repository holds 354 skills in this directory. The repository was last updated on October 7, 2026.

Source: borghei/Claude-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Test Scenarios

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Test Scenarios

When to use this skill

The 7 scenario categories

Clarify First

Workflow

Step 1 — Spec read

Step 2 — Happy path

Step 3 — Edge cases

Step 4 — Error handling

Step 5 — Empty / first-use / after-action states

Step 6 — Concurrent / race scenarios

Step 7 — Accessibility

Step 8 — Security + privacy

Step 9 — Run test_scenario_generator.py

Decision frameworks

How many scenarios per category?

Risk-weighted scenario selection

Manual vs automated

Common engagements

"Generate test scenarios for this new feature"

"Audit our test plan for completeness"

"Post-incident scenario gap analysis"

Anti-patterns to avoid

References

Related skills

Files

Compare with similar skills

Similar skills

More from borghei/Claude-Skills

Related

Questions about Test Scenarios

Step 9 — Run `test_scenario_generator.py`