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.

by phuryn 25k GitHub stars MIT Updated Jul 3, 2026
test-scenarios skill by phuryn
test-scenarios — Testing skill by phuryn

Overview

test-scenarios is an open-source testing skill for Claude Code and compatible agents, published by phuryn. Its author describes it as: “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 a…”. The project has 25k stars on GitHub and is available under the MIT license. Add it to your setup with `/plugin marketplace add phuryn/pm-skills`.

What test-scenarios does

Create comprehensive test scenarios from user stories with test objectives, starting conditions, user roles, step-by-step test actions, and expected outcomes.

Best for

What’s inside

The SKILL.md for test-scenarios is organised into these sections:

  • Step-by-Step Process
  • Scenario Template
  • Example Test Scenario
  • Output Deliverables

Installation

Add test-scenarios to your agent with:

/plugin marketplace add phuryn/pm-skills

Review a skill’s source before installing it — skills can instruct your agent to run commands. This command comes from the skill’s public repository, which is the source of truth for setup steps. New to skills? Read how to install Claude Code skills.

Supported agents

  • Claude Code — ships a claude code plugin marketplace

License

test-scenarios is published under the MIT license.

Strengths

  • Clear MIT license — safe to read and adapt within its terms
  • Ships in phuryn/pm-skills, an established project with 25,392 GitHub stars
  • Works with Claude Code
  • Actively maintained — repository updated in the last 90 days

Author

phuryn 41 skills in the catalog · GitHub profile ↗
View skills

Topics

Need a skill like this, tailored to your team?Build a custom skill →

Frequently asked questions

What does test-scenarios 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 /plugin marketplace add phuryn/pm-skills in your agent, then reload your skills. Review the source at https://github.com/phuryn/pm-skills before installing.
Is test-scenarios free to use?
Yes. test-scenarios is free and open source under the MIT license, so you can read, run, and adapt it within that license's terms.
Which agents does test-scenarios work with?
test-scenarios lists Claude Code — named in its SKILL.md, its plugin marketplace or its repository topics. Skills use the portable SKILL.md format, so other agents that read that format may load it too.
Where does test-scenarios come from?
test-scenarios ships inside phuryn/pm-skills, a repository that contains 41 catalogued skills in total. The repository's 25,392 GitHub stars apply to that whole collection, not to this skill on its own.

Analyze A/B test results with statistical significance, sample size validation, confidence intervals, and ship/extend/stop recommendations. Use when evaluating experiment results, checking if a test reached significance, interpreting split test data, or deciding whether to ship a variant.

Claude Code
25k GitHub stars MIT Updated Jul 3, 2026 Free

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.

Claude Code
25k GitHub stars MIT Updated Jul 3, 2026 Free

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.

Claude Code
25k GitHub stars MIT Updated Jul 3, 2026 Free

When the user wants to plan, design, or implement an A/B test or experiment. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "conversion experiment," "statistical significance," or "test this." For tracking implementation, see analytics-tracking.

Claude CodeCodexCursor+1
25k GitHub stars MIT Updated Aug 17, 2026 Free

Master end-to-end testing with Playwright and Cypress to build reliable test suites that catch bugs, improve confidence, and enable fast deployment. Use when implementing E2E tests, debugging flaky tests, or establishing testing standards.

Claude CodeCodexCursor+3
38k GitHub stars MIT Updated Jul 22, 2026 Free