Test scenarios help you check if a product works the way it should. This skill turns user stories into clear test steps. It gives you test objectives, starting conditions, user roles, and expected outcomes. Anyone on a QA team can use it to write test cases and plan feature validation.
You start by reviewing the user story and its acceptance criteria. Then you define what behavior to test and set up the system state. Next you identify who will perform the test and write step-by-step actions. Finally you list what should happen after each step. This makes sure you cover normal cases and edge cases.
The output is a set of ready-to-use test scenarios. Each scenario has a name, objective, conditions, role, steps, and expected results. Your QA team can take these and run them right away. This saves time and helps catch bugs before the product goes live.
Global
mkdir -p ~/.claude/skills/test-scenariosProject
mkdir -p .claude/skills/test-scenariosSource Repository
Grill Memattpocock/skills
Stress-test your plan with relentless questions until we both understand
Tddmattpocock/skills
Write one test at a time then code to make it pass
Test Driven Developmentobra/superpowers
Write a failing test first then code just enough to pass
Webapp Testinganthropics/skills
Test your local web apps quickly with Playwright automation and screenshots
Qamattpocock/skills
Turn bug reports into GitHub issues through natural conversation without technical fuss
Migrate To Shoehornmattpocock/skills
Replace unsafe as assertions with type-safe partial test data easily
Playwright Best Practicescurrents-dev/playwright-best-practices-skill
Master Playwright testing with best practices for reliable and fast tests
Google Agents Cli Evalgoogle/agents-cli
Run evaluations on your AI agent, find failures, and improve its quality step by step