Create comprehensive test scenarios from user stories with test objectives, starting conditions, user roles, step-by-step test actions, and expected outcomes.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versiontest-scenariosExecute the skills CLI command in your project's root directory to begin installation:
Fetches test-scenarios from phuryn/pm-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate test-scenarios. Access via /test-scenarios in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
0
total installs
0
this week
9.6K
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
9.6K
stars
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 constraintsTest Scenario: [Clear scenario name]
Test Objective: [What this test validates]
Starting Conditions:
User Role: [Who performs the test]
Test Steps:
Expected Outcomes:
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 Role: Online Shopper
Test Steps:
Expected Outcomes:
Prerequisites
Time Estimate
15-45 minutes depending on use case complexity
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
phuryn/pm-skills
phuryn/pm-skills
cexll/myclaude
github/awesome-copilot
github/awesome-copilot
dotnet/skills
I recommend test-scenarios for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
test-scenarios reduced setup friction for our internal harness; good balance of opinion and flexibility.
We added test-scenarios from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Useful defaults in test-scenarios — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Registry listing for test-scenarios matched our evaluation — installs cleanly and behaves as described in the markdown.
Keeps context tight: test-scenarios is the kind of skill you can hand to a new teammate without a long onboarding doc.
test-scenarios has been reliable in day-to-day use. Documentation quality is above average for community skills.
Useful defaults in test-scenarios — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
test-scenarios fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Registry listing for test-scenarios matched our evaluation — installs cleanly and behaves as described in the markdown.
showing 1-10 of 39