Test Scenarios
- 2k installs
- 24.9k repo stars
- Updated July 3, 2026
- phuryn/pm-skills
test-scenarios is an agent skill for "Create comprehensive test scenarios from user stories with test objectives, starting conditions, user roles, step-by-st
About
The test-scenarios skill "Create comprehensive test scenarios from user stories with test objectives, starting conditions, user roles, step-by-step actions, and expected outcomes. Use when writing QA test cases, creating test plans, defining acceptance tests, or preparing for feature validation." It covers $PRODUCT : The product or system name. Key workflows include $USER_STORY : The user story to test title and acceptance criteria. Developers invoke test-scenarios when the task matches the triggers and reference files in SKILL.md for grounded, stepwise execution. Reference files and progressive disclosure keep context focused while preserving concrete commands, configuration fields, and validation checks copied from the upstream documentation. Reference files and progressive disclosure keep context focused while preserving concrete commands, configuration fields, and validation checks copied from the upstream documentation. Reference files and progressive disclosure keep context focused while preserving concrete commands, configuration fields, and validation checks copied from the upstream documentation.
- $PRODUCT : The product or system name
- $USER_STORY : The user story to test title and acceptance criteria
- $CONTEXT : Additional testing context or constraints
- Review the user story and acceptance criteria
- Define test objectives - What specific behavior to validate
Test Scenarios by the numbers
- 1,997 all-time installs (skills.sh)
- +83 installs in the week ending Aug 5, 2026 (Skillselion tracking)
- Ranked #390 of 2,153 Testing & QA skills by installs in the Skillselion catalog
- Security screen: LOW risk (skills.sh audit)
- Data as of Aug 5, 2026 (Skillselion catalog sync)
test-scenarios capabilities & compatibility
- Capabilities
- $product : the product or system name · $user_story : the user story to test title and a · $context : additional testing context or constra · review the user story and acceptance criteria · define test objectives what specific behavior
- Use cases
- testing · debugging · documentation
What test-scenarios says it does
Create comprehensive test scenarios from user stories with test objectives, starting conditions, user roles, step-by-step test actions, and expected outcomes.
npx skills add https://github.com/phuryn/pm-skills --skill test-scenariosAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 2k |
|---|---|
| repo stars | ★ 24.9k |
| Security audit | 3 / 3 scanners passed |
| Last updated | July 3, 2026 |
| Repository | phuryn/pm-skills ↗ |
What problem does test-scenarios solve for developers using the documented workflows?
"Create comprehensive test scenarios from user stories with test objectives, starting conditions, user roles, step-by-step actions, and expected outcomes. Use when writing QA test cases, creating test
Who is it for?
Developers working with test-scenarios patterns described in the skill documentation.
Skip if: Skip when docs are empty or the task is outside the skill documented scope.
When should I use this skill?
Use when "Create comprehensive test scenarios from user stories with test objectives, starting conditions, user roles, step-by-step actions, and expected outcomes. Use when writing QA test
What you get
Actionable test-scenarios guidance grounded in SKILL.md workflows and reference files.
Files
Test Scenarios
Create comprehensive test scenarios from user stories with test objectives, starting conditions, user roles, step-by-step test actions, and expected outcomes.
Use when: Writing QA test cases, creating test plans, defining acceptance test scenarios, or validating user story implementations.
Arguments:
$PRODUCT: The product or system name$USER_STORY: The user story to test (title and acceptance criteria)$CONTEXT: Additional testing context or constraints
Step-by-Step Process
1. Review the user story and acceptance criteria 2. Define test objectives - What specific behavior to validate 3. Establish starting conditions - System state, data setup, configurations 4. Identify user roles - Who performs the test actions 5. Create test steps - Break down interactions step-by-step 6. Define expected outcomes - Observable results after each step 7. Consider edge cases - Invalid inputs, boundary conditions 8. Output detailed test scenarios - Ready for QA execution
Scenario Template
Test Scenario: [Clear scenario name]
Test Objective: [What this test validates]
Starting Conditions:
- [System state required]
- [Data or configuration needed]
- [User setup or permissions]
User Role: [Who performs the test]
Test Steps: 1. [First action and its expected result] 2. [Second action and observable outcome] 3. [Third action and system behavior] 4. [Completion action and final state]
Expected Outcomes:
- [Observable result 1]
- [Observable result 2]
- [Observable result 3]
Example Test Scenario
Test Scenario: View Recently Viewed Products on Product Page
Test Objective: Verify that the 'Recently viewed' section displays correctly and excludes the current product.
Starting Conditions:
- User is logged in or has browser history enabled
- User has viewed at least 2 products in the current session
- User is now on a product page different from previously viewed items
User Role: Online Shopper
Test Steps: 1. Navigate to any product page → Section should appear at bottom with previously viewed items 2. Scroll to bottom of page → "Recently viewed" section is visible with product cards 3. Verify product thumbnails → Images, titles, and prices are displayed correctly 4. Check current product → Current product is NOT in the recently viewed list 5. Click on a product card → User navigates to the corresponding product page
Expected Outcomes:
- Recently viewed section appears only after viewing at least 1 prior product
- Section displays 4-8 product cards with complete information
- Current product is excluded from the list
- Each card shows "Viewed X minutes/hours ago" timestamp
- Clicking cards navigates to correct product pages
- Performance: Section loads within 2 seconds
Output Deliverables
- Comprehensive test scenarios for each acceptance criterion
- Clear test objectives aligned with user story intent
- Detailed step-by-step test actions
- Observable expected outcomes after each step
- Edge case and error scenario coverage
- Ready for QA team execution and documentation
Related skills
TddFollow test-driven development with a strict red-green-refactor loop when creating reliable features or fixing bugs.544k196k
Test Driven DevelopmentEnforce writing failing tests before any production implementation code.181k264kQaRun conversational QA sessions that turn user-reported bugs into well-written, domain-aware GitHub issues without manual ticket writing.179k196kMigrate To ShoehornAutomatically update TypeScript test files that rely on unsafe `as` type assertions by replacing them with type-safe partial objects from @total-typescript/shoehorn.164k196k
Webapp TestingVerify frontend behavior, debug UI issues, capture screenshots, and inspect logs of a running local web application using Playwright.123k165k
Playwright CliRun browser automation, generate element snapshots, inspect DOM attributes, and execute Playwright tests from the terminal.102k12.3kFAQ
Who is test-scenarios for?
Developers and software engineers working with test-scenarios patterns described in the skill documentation.
When should I use test-scenarios?
When "Create comprehensive test scenarios from user stories with test objectives, starting conditions, user roles, step-by-step actions, and expected outcomes. Use when writing QA test .
Is test-scenarios safe to install?
Review the Security Audits panel on this page before installing in production.