Test Scenarios
Turn a user story and acceptance criteria into executable QA scenarios with preconditions, roles, steps, and expected outcomes before or right after you ship a feature.
Overview
Test Scenarios is an agent skill most often used in Ship (also Validate) that converts user stories and acceptance criteria into structured QA scenarios with objectives, preconditions, roles, steps, and expected outcomes
Install
npx skills add https://github.com/phuryn/pm-skills --skill test-scenariosWhat is this skill?
- 8-step process from user story review through edge cases and QA-ready output
- Scenario template with test objective, starting conditions, user roles, steps, and expected outcomes
- Accepts $PRODUCT, $USER_STORY, and $CONTEXT arguments for scoped scenario packs
- Explicit edge-case and boundary-condition coverage in the workflow
- Outputs detailed scenarios ready for QA execution without inventing automation code
- 8-step process from user story review through QA-ready scenario output
- Scenario template covering test objective, starting conditions, user roles, steps, and expected outcomes
Adoption & trust: 1.1k installs on skills.sh; 12.3k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You have user stories and acceptance criteria but no ordered, repeatable test scenarios your agent or QA can execute.
Who is it for?
Solo builders shipping SaaS, APIs, or apps who already have user stories and need a formal test plan or acceptance-test pack before release.
Skip if: Teams that only need automated E2E scripts with no written scenarios, or builds with no user story or acceptance criteria defined yet.
When should I use this skill?
Writing QA test cases, creating test plans, defining acceptance test scenarios, or preparing for feature validation from user stories.
What do I get? / Deliverables
You get named test scenarios with objectives, starting conditions, role-based steps, expected outcomes, and edge cases—ready to run manually or to seed automated tests.
- Named test scenarios with objectives and starting conditions
- Step-by-step test actions with expected outcomes per step
- Edge-case and boundary-condition scenarios for the user story
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Ship is the canonical shelf because the skill explicitly targets QA test cases, test plans, and pre-release validation—the core testing subphase of getting software out safely. Testing subphase matches writing test cases, defining step-by-step actions, and locking expected outcomes for manual or structured QA execution.
Where it fits
Draft acceptance-test scenarios from a scoped user story before you commit engineering time to the full build.
Validate a clickable prototype by turning demo flows into step-by-step scenarios with expected UI outcomes.
Expand the test plan for a release candidate with edge cases and role-based paths before manual QA sign-off.
Attach scenario checklists to a PR so reviewers know which acceptance paths must pass before merge.
Reuse regression scenarios when support reports a bug tied to a specific user story acceptance criterion.
How it compares
Use for structured scenario documents from stories instead of ad-hoc “test this in chat” checklists.
Common Questions / FAQ
Who is test-scenarios for?
Solo and indie builders, and small teams using AI coding agents, who need QA-ready test scenarios derived from product user stories without hiring a full-time test lead.
When should I use test-scenarios?
Use it when writing QA test cases, creating test plans, defining acceptance test scenarios, or validating a user story implementation—especially in Validate when locking acceptance criteria and in Ship when preparing feature validation before release.
Is test-scenarios safe to install?
It is a documentation and planning skill with no built-in shell or network actions described in SKILL.md; review the Security Audits panel on this Prism page before installing any skill from the registry.
SKILL.md
READMESKILL.md - Test Scenarios
# 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