test-scenarios

Provide the user story with its acceptance criteria, and the Skill generates test scenarios covering objectives, preconditions, user roles, numbered steps, and expected results. Each acceptance criterion maps to verifiable test steps that QA can execute directly.

A complete test scenario includes a clear test objective, preconditions such as system state and required data, the user role performing the test, step-by-step actions with observable results, and expected outcomes. Edge cases and error conditions should also be covered.

Yes, the Skill is designed for defining acceptance tests from user stories in agile workflows. It aligns each test objective with the story's acceptance criteria so scenarios verify the intended behavior before release.

No, it produces human-readable test scenarios for manual QA execution and documentation. The output can serve as a specification for writing automated tests in frameworks like Selenium or Playwright, but it does not generate executable test code.

Three inputs are accepted: the product or system name, the user story with title and acceptance criteria, and optional testing context or constraints. The more complete the acceptance criteria, the more thorough the generated scenario coverage.