Test Scenarios

CommunityPopular

phuryn

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.

Overview

Publisher	phuryn
Repository	`pm-skills`
Skill name	`test-scenarios`
Stars	26.4K
Forks	2.8K
Bundled files	Instructions only
License	MIT
Links	Skill source Repository Homepage

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
Self-contained
Everything the model needs lives in the instructions — no extra files to sync.
Open source
Published by phuryn on GitHub. Read the source before you install it.

Installation

Install the Test Scenarios AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
Enable the skill in any chat where you want it available.

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/phuryn/pm-skills.git /tmp/pm-skills
mkdir -p .claude/skills
cp -r /tmp/pm-skills/pm-execution/skills/test-scenarios .claude/skills/test-scenarios

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Test Scenarios in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Test Scenarios on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Test Scenarios is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

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

Frequently asked questions

What does the Test Scenarios AI skill do?

Why use Test Scenarios on TypingMind?

Because you install it once and use it with any model. Test Scenarios is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Test Scenarios in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/phuryn/pm-skills/tree/main/pm-execution/skills/test-scenarios. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Test Scenarios?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Test Scenarios?

As many as you like. As long as a model supports skills, you can use Test Scenarios with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Test Scenarios AI skill free?

Yes. It is published on GitHub by phuryn under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Benchmark

garrytan

CommunityPopular

Performance regression detection. (gstack)

Ios Design Review

Visual design audit for iOS apps on real hardware. (gstack)

Ios Fix

Autonomous iOS bug fixer. (gstack)

Ios Qa

Live-device iOS QA for SwiftUI apps. (gstack)

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Test Scenarios

Step-by-Step Process

Scenario Template

Example Test Scenario

Output Deliverables

Frequently asked questions

Related AI Skills

Set up your own AI workspace now