What is test-scenarios?

A template and process for creating detailed software test scenarios from a user story. A test scenario describes the setup, user actions, expected results, and edge cases to check.

Use it to prepare QA test cases, acceptance tests, starting conditions, user roles, step-by-step actions, expected outcomes, and boundary-case checks.

It turns a feature description into repeatable checks, making it clearer what must work before the feature is accepted.

test-scenarios — Skill for Claude Code by unixcrh

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add unixcrh/phuryn-pm-skills --skill test-scenarios

Clone the repo

git clone --depth 1 https://github.com/unixcrh/phuryn-pm-skills

Made for: Claude Code.

Or install pm-execution, the plugin that ships this one along with the rest of its 15 skills, 10 commands.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/unixcrh/phuryn-pm-skills/test-scenarios/github.svg)](https://agentmods.dev/skills/unixcrh/phuryn-pm-skills/test-scenarios)

Your own site

<a href="https://agentmods.dev/skills/unixcrh/phuryn-pm-skills/test-scenarios"><img src="https://agentmods.dev/badge/skills/unixcrh/phuryn-pm-skills/test-scenarios/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/unixcrh/phuryn-pm-skills/test-scenarios"><img src="https://agentmods.dev/badge/skills/unixcrh/phuryn-pm-skills/test-scenarios.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 52 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 715 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin 100% copy Near-identical to another mod in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00052	$0.00715
Opus 5	$0.00026	$0.00358
Sonnet 5	$0.00010	$0.00143
Haiku 4.5	$0.00005	$0.00072

Measured 12d ago against content hash 2dc10ebb6359, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

test-scenarios scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 12d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

Origin

This is a copy

100% identical to test-scenarios — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

pm-execution/skills/test-scenarios/SKILL.md · 87 lines

How it starts

The opening of the file, as written. The whole thing — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.

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

Read the full file on GitHub · 87 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

12d ago First seen · 87 lines · 52 tokens per session scan A 2dc10ebb6359

Subscribe to this mod's changes

test-scenarios is a skill published in the GitHub repository unixcrh/phuryn-pm-skills (2 stars, last pushed 6mo ago), licensed MIT. It adds 52 tokens to every session and 715 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to test-scenarios, differing in 0 lines, and is treated as a copy.

Testing

research-engineer

An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.

davila7/claude-code-templates · 43 tokens

tika-eval-compare

Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".

apache/tika · 50 tokens

neuron-evaluation-engineer

Create and run AI evaluations with datasets, assertions, and output drivers in Neuron AI. Use this skill whenever the user mentions evaluation, testing AI systems, creating evaluators, dataset-driven testing, assertion-based validation, or wants to measure AI system performance. Also trigger for tasks involving…

neuron-core/neuron-ai · 77 tokens

test-scenarios