test-scenarios
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.
- Installs
- 2.9K
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/phuryn/pm-skills --skill test-scenarios- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads test-scenarios automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
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
- Review the user story and acceptance criteria
- Define test objectives - What specific behavior to validate
- Establish starting conditions - System state, data setup, configurations
- Identify user roles - Who performs the test actions
- Create test steps - Break down interactions step-by-step
- Define expected outcomes - Observable results after each step
- Consider edge cases - Invalid inputs, boundary conditions
- 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:
- [First action and its expected result]
- [Second action and observable outcome]
- [Third action and system behavior]
- [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:
- Navigate to any product page → Section should appear at bottom with previously viewed items
- Scroll to bottom of page → "Recently viewed" section is visible with product cards
- Verify product thumbnails → Images, titles, and prices are displayed correctly
- Check current product → Current product is NOT in the recently viewed list
- 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
FAQ
What does the test-scenarios skill do?
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.
How do I install test-scenarios?
Run npx skills add https://github.com/phuryn/pm-skills --skill test-scenarios in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/test-scenarios/ (personal) or .claude/skills/test-scenarios/ (project).
Which AI agents can use test-scenarios?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is test-scenarios safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains test-scenarios?
It is published by phuryn in phuryn/pm-skills. It has 2,913 recorded installs.
More from phuryn/pm-skills
create-prd
phuryn/pm-skills
Create a lean, decision-ready Product Requirements Document with an 8-section template: summary, contacts, background, objective, market segments, value propositions (6-part JTBD template), solution, and release. Lean by default (about one to two pages), with a fuller spec on request. Use when writing a PRD, documenting product requirements, preparing a feature spec, or reviewing an existing PRD.
pre-mortem
phuryn/pm-skills
Run a pre-mortem risk analysis on a PRD or launch plan. Categorizes risks as Tigers (real problems), Paper Tigers (overblown concerns), and Elephants (unspoken worries), then classifies as launch-blocking, fast-follow, or track. Use when preparing for launch, stress-testing a product plan, or identifying what could go wrong.
prioritization-frameworks
phuryn/pm-skills
Reference guide to 9 prioritization frameworks with formulas, when-to-use guidance, and templates — RICE, ICE, Kano, MoSCoW, Opportunity Score, and more. Use when selecting a prioritization method, comparing frameworks like RICE vs ICE, or learning how different prioritization approaches work.
outcome-roadmap
phuryn/pm-skills
Transform an output-focused roadmap into an outcome-focused one that communicates strategic intent. Rewrites initiatives as outcome statements reflecting user and business impacts. Use when shifting to outcome roadmaps, making a roadmap more strategic, or rewriting feature lists as outcomes.
strategy-red-team
phuryn/pm-skills
Red-team a PRD, roadmap, or strategy by attacking its load-bearing assumptions before reality does. Steelmans then attacks each claim, ranks failure modes by impact × likelihood × cheapness-to-test, and returns the cheapest test and kill criteria for each. Use when stress-testing a plan, pressure-testing a strategy, challenging assumptions, or preparing a doc for executive review.
competitor-analysis
phuryn/pm-skills
Analyze competitors with strengths, weaknesses, and differentiation opportunities. Identifies direct competitors and maps the competitive landscape. Use when doing competitive research, preparing a competitive brief, or finding differentiation opportunities.
Popular testing & qa skills
tdd
mattpocock/skills
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
grilling
mattpocock/skills
Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.
migrate-to-shoehorn
mattpocock/skills
Migrate test files from as type assertions to @total-typescript/shoehorn. Use when user mentions shoehorn, wants to replace as in tests, or needs partial test data.
run-train
lllllllama/rigorpilot-skills
Rigor Train skill for deep learning research repositories. Use when a documented or selected training command should be run conservatively for startup verification, short-run verification, full kickoff, or resume, with command, config, seed, log, checkpoint, status, and metric evidence written to standardized trainoutputs/. Do not use for environment setup, exploratory sweeps, speculative idea implementation, or end-to-end orchestration.
test-driven-development
obra/superpowers
Use when implementing any feature or bugfix, before writing implementation code
finishing-a-development-branch
obra/superpowers
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work