MaVoid-Team/test-scenarios
Agent-Skills/PM-Skills/skills/test-scenarios/SKILL.md
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.
testing
Updated Apr 16, 2026
$ install --global
skillsauthnpx skillsauth add MaVoid-Team/Capital-Consultancy-Final test-scenariosInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
4 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
4
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 30, 2026, 3:32 PM28.2s1 file scanned
SKILL.md
- name:
- test-scenarios
- description:
- 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.
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
Related Skills
MaVoid-Team/wwas
development
VerifiedTrustedCommunity
Create product backlog items in Why-What-Acceptance format — independent, valuable, testable items with strategic context. Use when writing structured backlog items, breaking features into work items, or using the WWA format.
SKILL.mdUpdated Apr 16, 2026
MaVoid-Team/user-stories
content-media
VerifiedTrustedCommunity
Create user stories following the 3 C's (Card, Conversation, Confirmation) and INVEST criteria with descriptions, design links, and acceptance criteria. Use when writing user stories, breaking down features into backlog items, or defining acceptance criteria.
SKILL.mdUpdated Apr 16, 2026
MaVoid-Team/summarize-meeting
testing
VerifiedTrustedCommunity
Summarize a meeting transcript into structured notes with date, participants, topic, key decisions, summary points, and action items. Use when processing meeting recordings, creating meeting notes, writing meeting minutes, or recapping discussions.
SKILL.mdUpdated Apr 16, 2026
MaVoid-Team/stakeholder-map
development
VerifiedTrustedCommunity
Build a stakeholder map using a power/interest grid, identify communication strategies per quadrant, and generate a communication plan. Use when managing stakeholders, preparing for a launch, aligning cross-functional teams, or planning stakeholder engagement.
SKILL.mdUpdated Apr 16, 2026