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.

Quality

77%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./pm-execution/skills/test-scenarios/SKILL.md

Quality

Content

61%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is well-structured with a concrete template and a strong worked example, but it is padded with redundant framing and lacks validation checkpoints that would make the workflow self-verifying. Trimming the duplicated intro and deliverables sections would free budget for the missing edge-case guidance.

Suggestions

Remove the opening paragraph and 'Output Deliverables' section, which duplicate the frontmatter description and the process/template, or replace the deliverables list with a single 'Each acceptance criterion maps to at least one scenario' check.

Add an explicit validation checkpoint to the process, e.g., after step 8: 'Verify every acceptance criterion is covered by at least one scenario and every step has an observable expected outcome before finishing.'

Ground the 'Consider edge cases' step by adding one edge-case scenario to the example (e.g., empty recently-viewed history or a session with only the current product viewed), so the guidance is demonstrable rather than a one-line mention.

Dimension	Reasoning	Score
Conciseness	The opening paragraph repeats the frontmatter description nearly verbatim, and the 'Output Deliverables' section ('Comprehensive test scenarios...', 'Clear test objectives...', 'Detailed step-by-step test actions...') restates the process and template without adding new information; the core template and example themselves are tight.	3 / 5
Actionability	Provides a concrete scenario template with placeholders plus a fully worked example with observable per-step results, which is appropriately actionable for an instruction-only skill; the gap is that 'Consider edge cases' appears in the process but edge cases never appear in the template or example.	4 / 5
Workflow Clarity	The 8-step process is clearly sequenced, but there are no validation checkpoints (e.g., verifying each acceptance criterion maps to at least one scenario), and step 8 ('Output detailed test scenarios') restates the goal rather than acting as a checkpoint.	3 / 5
Progressive Disclosure	No bundle files exist and none are needed; the body is self-contained with well-organized sections (process, template, example). It falls short of a 5 because at ~82 lines the padded deliverables section adds no navigational value beyond the simple-skill case.	4 / 5
	Total	14 / 20 Passed

Description

83%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description with a clear what/when pair and mostly natural trigger terms. Its main gaps are incomplete synonym coverage and a single decomposed action rather than multiple distinct capabilities.

Dimension	Reasoning	Score
Specificity	Enumerates several concrete components ('test objectives, starting conditions, user roles, step-by-step actions, and expected outcomes'), but this is one action (create test scenarios) decomposed into parts rather than multiple distinct top-level actions, leaving minor gaps in coverage.	4 / 5
Completeness	Explicitly answers both: what ('Create comprehensive test scenarios from user stories with test objectives, starting conditions, user roles, step-by-step actions, and expected outcomes') and when ('Use when writing QA test cases, creating test plans, defining acceptance tests, or preparing for feature validation') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Includes natural phrases users would say ('writing QA test cases', 'creating test plans', 'defining acceptance tests'), but misses common variations such as 'test scenarios', 'acceptance criteria', or 'user story testing', so coverage is good rather than comprehensive.	4 / 5
Distinctiveness Conflict Risk	The QA test-scenario niche is clearly carved out with distinct triggers, but phrases like 'validating user story implementations' carry minor overlap risk with general test-writing or code-testing skills.	4 / 5
	Total	17 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: phuryn/pm-skills
Path: pm-execution/skills/test-scenarios/SKILL.md
Commit: 8607e3b

Reviewed: 6 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.