test-scenarios

Generate test scenarios from user stories with objectives, steps, and expected outcomes.

Updated Mar 7, 2026

Search Tags:#testing #validation #qa #acceptance criteria #user stories #test scenarios

Ready to run

npx skills add https://github.com/shalevamin/The-_Ultimate_agents --skill test-scenarios-shalevamin

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: test-scenarios
Source: https://github.com/shalevamin/The-_Ultimate_agents/tree/main/.claude/skills/test-scenarios
Command: npx skills add https://github.com/shalevamin/The-_Ultimate_agents --skill test-scenarios-shalevamin

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the creation of detailed test scenarios from user stories, ensuring comprehensive test coverage and clear validation steps for software development.

Core Features & Use Cases

Test Scenario Generation: Creates structured test cases including objectives, starting conditions, roles, steps, and expected outcomes.
Use Case: A product manager provides a user story for a new e-commerce checkout feature. This Skill generates multiple test scenarios covering happy paths, edge cases, and error conditions for the QA team to execute.

Quick Start

Use the test-scenarios skill to create test scenarios for the user story "As a user, I want to reset my password so that I can access my account if I forget it."

Frequently Asked Questions about test-scenarios

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I generate test scenarios from user stories automatically?▼

To generate test scenarios from user stories, you provide a clear user story and optional context. The tool then structures detailed validation cases including objectives, starting conditions, user roles, step-by-step actions, and expected outcomes.

What should be included in QA acceptance criteria for test case writing?▼

QA acceptance criteria for test case writing should include distinct objectives, starting conditions, user roles, step-by-step actions, and expected outcomes. This ensures comprehensive coverage of happy paths, edge cases, and error conditions for validation.

Can I create a test plan covering edge cases from a single user story?▼

Yes, you can create a test plan covering edge cases from a single user story. By supplying the user story and optional context, the generation process outputs multiple scenarios addressing happy paths, edge cases, and error conditions.

What is the best way to write acceptance test definitions for new features?▼

The best way to write acceptance test definitions is to derive structured scenarios directly from user stories. This approach details starting conditions, roles, actions, and expected outcomes to ensure clear validation steps and comprehensive test coverage.

Do I need to provide detailed context to generate test cases for QA?▼

You need a clear user story input as a minimum requirement to generate test cases for QA. Providing optional context alongside the user story helps construct more effective and accurate validation scenarios for the software.

Why does my test scenario generation lack edge case coverage?▼

Test scenario generation may lack edge case coverage if the input user story is unclear or lacks optional context. Supplying detailed context ensures the generation of comprehensive scenarios including error conditions and edge cases.