New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Test Scenarios

by phuryn in phuryn/pm-skills

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

MITAuto-check passedTesting & QA

Install Test Scenarios

skills CLI
$ npx skills add phuryn/pm-skills --skill test-scenarios -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install phuryn/pm-skills test-scenarios --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/phuryn/pm-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/pm-execution/skills/test-scenarios .claude/skills/test-scenarios && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
test-scenarios
GitHub stars
27k
Token cost
~866 tokens
SKILL.md length
427 words
Files
1
Skills in repo
67
Repo updated
First seen
Licence
MIT

At a glance

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

  • Works in 8 steps: Review the user story and acceptance… → Define test objectives - What specific… → Establish starting conditions - System… → …
  • Writing QA test cases
  • SKILL.md covers Step-by-Step Process, Scenario Template, Example Test Scenario and Output Deliverables
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Test Scenarios is an agent skill from phuryn/pm-skills. 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.

Its SKILL.md is about 870 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Testing & QA, covering Test generation, User stories and End-to-end testing. The repository describes itself as: PM Skills Marketplace: 100+ agentic skills, commands, and plugins — from discovery to strategy, execution, launch, and growth. The licence is MIT.

When your agent uses it

  • Writing QA test cases
  • Creating test plans
  • Defining acceptance tests
  • Preparing for feature validation

Example prompts

  • “/test-scenarios”

Workflow steps

8 steps, taken from the first numbered list in SKILL.md.

  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

What it can do on your machine

Read from SKILL.md and the folder at commit 6058e29. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Test Scenarios loads about 866 tokens when it runs. Until then it costs about 71 tokens; SKILL.md has 427 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~71
When it runs · the whole SKILL.md, loaded when a task matches
~866

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from phuryn/pm-skills at commit 6058e29, republished under its MIT licence (© phuryn). 427 words, ~866 tokens.

Download SKILL.mdSave it as .claude/skills/test-scenarios/SKILL.md (or your agent's skills folder).
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

  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]
Show full SKILL.md (223 more words)Show less

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

© phuryn, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in pm-execution/skills/test-scenarios of phuryn/pm-skills.

Open the folder on GitHubat commit 6058e29

Compare with similar skills

Test Scenarios next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Test Scenarios compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Test Scenarios this skillphuryn/pm-skills27k—~866Automated safety check: PassMIT
Argent QA Flowsbbplayer-app/BBPlayer1.2k—~3.2kAutomated safety check: PassMIT
Plan Testsgenkovich/sdd171—~3.1kAutomated safety check: PassMIT
Test Authorjpicklyk/task-orchestrator207—~8.2kAutomated safety check: PassMIT
Test Case Writermohitagw15856/pm-claude-skills1.4k—~970Automated safety check: PassMIT
Add E2E Test Suitecrowdin/crowdin-cli320—~2.4kAutomated safety check: PassMIT

Similar skills

  • Argent QA Flows

    bbplayer-app/BBPlayer

    Create repeatable QA regression E2E tests as Argent flows from test cases, tickets, or acceptance criteria.

    1.2k GitHub stars~3.2k tokensUpdated 2 days ago
    Testing & QAAuto-check passed

  • Plan Tests

    genkovich/sdd

    A skill your agent uses to turn a feature's acceptance criteria into a test plan before any test is written — a table that maps every spec.md §5 acceptance criterion to at least one test, names the…

    171 GitHub stars~3.1k tokensUpdated 1 mo ago
    Testing & QAAuto-check passed

  • Test Author

    jpicklyk/task-orchestrator

    Test authoring framework for items carrying the needs-test-author trait.

    207 GitHub stars~8.2k tokensUpdated today
    Testing & QAAuto-check passed

  • Test Case Writer

    mohitagw15856/pm-claude-skills

    Turn a requirement or user story into clear, executable test cases.

    1.4k GitHub stars~970 tokensUpdated yesterday
    Testing & QAAuto-check passed

  • Add E2E Test Suite

    crowdin/crowdin-cli

    Adds a new end-to-end (e2e) test suite for the Crowdin CLI under tests/e2e/suites/, exercising real CLI commands against a freshly-created Crowdin project.

    320 GitHub stars~2.4k tokensUpdated yesterday
    Testing & QAAuto-check passed

  • E2E Test Thinker

    UniClipboard/UniClipboard

    Analyze the current branch's diff against main and determine which changes are testable via CLI-based end-to-end tests.

    1.9k GitHub stars~1.7k tokensUpdated today
    Testing & QAAuto-check passed

More from phuryn/pm-skills

All 67 skills in this repo

  • Agreement-Based Code Review

    phuryn/pm-skills

    Reviews a diff by anchoring on agreements between two sides of a boundary, forcing a concrete violating execution, and refuting each finding before reporting it.

    27k GitHub stars~3.6k tokensUpdated yesterday
    Auto-check passed

  • A/B Test Analysis

    phuryn/pm-skills

    Validates an experiment's setup, works out lift, p-value and confidence interval from A/B test data, and recommends whether to ship, extend or stop.

    27k GitHub stars~893 tokensUpdated yesterday
    Auto-check passed

  • Team OKR Brainstorm

    phuryn/pm-skills

    Drafts three alternative sets of team OKRs, each with an inspiring objective and measurable key results, tied to the company strategy you provide.

    27k GitHub stars~1.1k tokensUpdated yesterday
    Auto-check passed

  • Cohort Analysis and Retention Explorer

    phuryn/pm-skills

    Analyzes uploaded cohort data to compute retention curves and feature adoption trends, builds heatmaps and charts, and suggests qualitative follow-up research.

    27k GitHub stars~1.3k tokensUpdated yesterday
    Auto-check passed

  • Dummy Dataset Generator

    phuryn/pm-skills

    Generates realistic test datasets with custom columns, row counts and business constraints, output as CSV, JSON, SQL inserts or a runnable Python script.

    27k GitHub stars~983 tokensUpdated yesterday
    Auto-check passed

  • Grammar and Flow Checker

    phuryn/pm-skills

    Reviews a draft for grammar, logic and flow problems and returns located, prioritized fix suggestions without rewriting the whole text.

    27k GitHub stars~2.4k tokensUpdated yesterday
    Auto-check passed

Categories

Questions about Test Scenarios

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. Test Scenarios is an agent skill from phuryn/pm-skills. Create comprehensive test scenarios from user stories with test objectives, starting conditions, user roles, step-by-step actions, and expected outcomes.

When should I use Test Scenarios?

Test Scenarios fits situations like: writing QA test cases; creating test plans; defining acceptance tests; preparing for feature validation.

How do I install Test Scenarios in Claude Code?

Run `npx skills add phuryn/pm-skills --skill test-scenarios -a claude-code`. Or copy the skill folder (pm-execution/skills/test-scenarios in phuryn/pm-skills) into .claude/skills/test-scenarios in your project. Claude Code loads it when a task matches its description.

How do I install Test Scenarios in Codex?

Run `npx skills add phuryn/pm-skills --skill test-scenarios -a codex`. Or copy the skill folder (pm-execution/skills/test-scenarios in phuryn/pm-skills) into .agents/skills/test-scenarios in your project. Codex loads it when a task matches its description.

Can I use Test Scenarios in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add phuryn/pm-skills --skill test-scenarios -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/test-scenarios, .gemini/skills/test-scenarios, .github/skills/test-scenarios and .opencode/skills/test-scenarios in your project.

What does Test Scenarios need to run?

SKILL.md names no scripts, command-line tools or credentials: Test Scenarios is instructions for the agent only.

Does Test Scenarios access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Test Scenarios safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Test Scenarios use?

Test Scenarios is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Test Scenarios use?

About 866 tokens (SKILL.md is roughly 3.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Test Scenarios?

Skills that share tags, products or a category with Test Scenarios: Argent QA Flows (bbplayer-app/BBPlayer, 1.2k stars), Plan Tests (genkovich/sdd, 171 stars), Test Author (jpicklyk/task-orchestrator, 207 stars) and Test Case Writer (mohitagw15856/pm-claude-skills, 1.4k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Test Scenarios?

phuryn (a GitHub user) maintains it in phuryn/pm-skills, which has 26,862 GitHub stars. The repository holds 67 skills in this directory. The repository was last updated on October 9, 2026.

Source: phuryn/pm-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.