skills.rest
moonzff
moonzffCOMMUNITY
Explore all skills by this author →
GitHub

test-scenarios

Generate structured QA test scenarios from user stories with steps and expected outcomes.

1|Updated May 6, 2026
Search Tags:#qa#acceptance criteria#user stories#test cases#test scenarios#test planning
One-click install
npx skills add https://github.com/moonzff/Codex_up --skill test-scenarios-moonzff
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: test-scenarios
Source: https://github.com/moonzff/Codex_up/tree/main/skills/product-planning/test-scenarios
Command: npx skills add https://github.com/moonzff/Codex_up --skill test-scenarios-moonzff

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing thorough, executable test cases from user stories is time-consuming and often inconsistent. This Skill turns a user story and its acceptance criteria into detailed, ready-to-run test scenarios with objectives, preconditions, roles, steps, and expected outcomes. ## Core Features & Use Cases - Structured Scenario Generation: Produces test scenarios with objectives, starting conditions, user roles, step-by-step actions, and observable expected outcomes. - Edge Case Coverage: Prompts consideration of invalid inputs, boundary conditions, and error scenarios beyond the happy path. - Use Case: Given a user story like "As a shopper, I want to see recently viewed products", the Skill outputs a complete scenario including setup state, navigation steps, exclusion rules for the current product, and performance expectations. ## Quick Start Ask the assistant to create test scenarios for your user story, providing the story title, acceptance criteria, and any testing constraints.

Frequently Asked Questions about test-scenarios

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

FAQPage Schema
How do I write test scenarios from user stories?▼

Provide the user story title and acceptance criteria, and the Skill generates scenarios covering test objectives, starting conditions, user roles, step-by-step actions, and expected outcomes. Each acceptance criterion maps to one or more executable scenarios.

What should a good test scenario include?▼

A complete test scenario includes a clear objective, starting conditions describing system state and data setup, the user role performing the test, numbered steps with expected results per action, and final observable outcomes including edge cases.

Can I use this for acceptance test definition in agile teams?▼

Yes, the output format aligns with acceptance test practices: scenarios derive directly from acceptance criteria and are written for QA execution. They work for sprint planning, story validation, and test documentation.

Does it cover edge cases and negative testing?▼

The process explicitly includes a step for edge cases such as invalid inputs and boundary conditions. However, coverage depth depends on the acceptance criteria provided, so include constraints and error requirements in your input for best results.

What input do I need to provide to generate test cases?▼

At minimum, provide the user story with its acceptance criteria. Optionally add the product or system name and testing context or constraints. Missing inputs that materially affect results will be requested before generation.

Related Skills

Explore More Product & Management Skills→
AbsolutelySkilledAbsolutelySkilled
207

user-stories

Generate user stories and acceptance criteria using INVEST and Given/When/Then templates.

Official
Advanced
s0613s0613
1

test-scenario

Generate, execute, and track feature test scenarios with pass rate tracking.

Community
Advanced
LucaDeLeoLucaDeLeo
1

dogfood

Explore web apps through structured testing with evidence capture.

Community
Advanced
pantheon-orgpantheon-org
9

bdd-testing

Create and run Cucumber BDD tests using Gherkin syntax and feature files.

Official
Advanced