Skip to content
SkillModel-led662 tokens in use

test-scenarios

Create QA test scenarios from a user story with objectives, starting conditions, steps, expected outcomes and edge cases.

28,201 stars on the repository MIT Licensephuryn/pm-skills · pm-execution/skills/test-scenarios
claude plugin install pm-execution@pm-skills
View source

Install command as written in the repository's README

Skill label

measured from its files

What installing test-scenarios costs

51tokens idle
662tokens in use

Idle is what sits in context while the skill is installed. In use is its instructions, loaded when it runs. Counts are approximate, made offline with cl100k_base.

Model dependence Model-led

Script-ledMixedModel-led

Mostly instructions, so how well it works depends on the model that follows them.

This describes the skill's structure, how much of it is scripts. It does not say how well it works.

Touches

Nothing detected: no shell, network, file writes, git or credentials in its files.

Declared tags come from the skill's frontmatter; detected ones from its scripts, its code blocks and the commands it names in inline code. This is detected, not audited.

How it scores

Quality

How well the skill is written, counted from its own files: its frontmatter, its steps, examples, stated output and constraints, its size and whether every file it ships is one it names.How we score it →
Good
  • Frontmatter12/15
  • Structure23/25
  • Examples6/15
  • Output12/15
  • Size15/15
  • Resources10/15

Security

Starts at 100 and loses points for each thing in the skill's files that a reader should look at first.How we score it →
Excellent

No findings.

Repository health

Pre-computed score based on development activity, maintenance, community, maturity, and trend momentum.How we score it →
Good
  • Development activity80
  • Maintenance76
  • Community60
  • Maturity32
  • Momentum40

test-scenarios takes a product name, a user story with its acceptance criteria and any testing context, and produces scenarios a QA team can execute. Each scenario has a name, a test objective, starting conditions, the user role, numbered steps and expected outcomes.

It follows an eight-step process that covers the story, objectives, system state, roles, steps, outcomes, edge cases such as invalid inputs and boundary conditions, and the final write-up.

What You Get

  • Test scenarios for each acceptance criterion
  • A test objective tied to the intent of the user story
  • Starting conditions covering system state, data and permissions
  • Step-by-step actions with an observable outcome after each
  • Edge case and error scenarios
  • Output ready for QA execution and documentation

Common Use Cases

  • Writing QA cases for a new feature
  • Defining acceptance tests from a user story
  • Preparing a feature for validation before release

What Makes It Unique

Each scenario states its starting conditions and user role up front, and every step carries the result expected at that point. Edge cases and error handling are an explicit step in the process.

Under The Hood

The skill is one SKILL.md of instructions with no scripts. It takes the product, user story and context as arguments, reasons from them and writes the scenarios in its reply. It does not read other files or call external services.

Join founders building with open source

Opinionated takes, migration guides, cost-saving tips, and insights from the open source ecosystem.

Subscribe on SubstackJoin 750+ subscribers