test-scenarios

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

25.0k|2.7k|Updated Mar 1, 2026
One-click install
npx skills add https://github.com/phuryn/pm-skills --skill test-scenarios-phuryn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-scenarios
Source: https://github.com/phuryn/pm-skills/tree/main/pm-execution/skills/test-scenarios
Command: npx skills add https://github.com/phuryn/pm-skills --skill test-scenarios-phuryn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the creation of comprehensive test scenarios from user stories, ensuring thorough validation and quality assurance for software features.

Core Features & Use Cases

  • Scenario Generation: Creates detailed test scenarios including objectives, starting conditions, user roles, step-by-step actions, and expected outcomes.
  • QA Readiness: Provides structured test cases ready for execution by QA teams.
  • Use Case: When a new user story for a login feature is defined, use this Skill to generate all necessary test scenarios, covering happy paths, edge cases, and error conditions.

Quick Start

Use the test-scenarios skill to generate 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?

To generate test scenarios from user stories, input a clear user story and optional context to produce detailed test scenarios covering test objectives, starting conditions, user roles, step-by-step actions, and expected outcomes for feature validation.

What is the best way to write acceptance criteria test cases for QA?

Writing acceptance criteria test cases is best handled by automating scenario generation from user stories, which structures test objectives, starting conditions, and step-by-step actions to cover happy paths, edge cases, and error conditions for QA teams.

Do I need fully detailed user stories to create valid test plans?

You need clear user story input and optional context to create valid test plans and test scenarios. Without clear user stories, the generated step-by-step actions and expected outcomes may lack the necessary detail for feature validation.

Can test scenario generation cover edge cases and error conditions?

Test scenario generation can cover edge cases and error conditions. It automates comprehensive test scenario creation from user stories, ensuring thorough validation by detailing test objectives and expected outcomes for both happy paths and error conditions.

What are the limitations of automated test case generation?

A limitation of automated test case generation is its reliance on receiving clear user story input. If the user story lacks detail or context, the resulting test scenarios, step-by-step actions, and expected outcomes may be incomplete for QA execution.