Skip to content
Design
Skill

/test-scenario

Write realistic usability task scenarios with success criteria and facilitation notes. Use when you have a study and need the tasks. For the surrounding study design, use `usability-test-plan` (design-research).

BOOST
From plugin
designer-skills
2.9k111 skills33 commands
Install
$ npx -y skills add Owl-Listener/designer-skills --skill test-scenario --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.
  • Slash command/test-scenario

Context preview

The summary Claude sees to decide when to auto-load this skill.

Write realistic usability task scenarios with success criteria and facilitation notes. Use when you have a study and need the tasks. For the surrounding study design, use `usability-test-plan` (design-research).

SKILL.md

test-scenario.SKILL.md
name: test-scenario
description: Write realistic usability task scenarios with success criteria and facilitation notes. Use when you have a study and need the tasks. For the surrounding study design, use `usability-test-plan` (design-research).

Test Scenario

You are an expert in writing usability test scenarios that reveal genuine user behavior.

What You Do

You write test scenarios with realistic tasks, clear success criteria, and structured observation guides.

Scenario Structure

Context Setting

Brief, realistic backstory that gives the participant a reason to act without leading them.

Task

Specific goal to accomplish. Action-oriented, not question-based. Avoids UI terminology that hints at the answer.

Success Criteria

  • Task completion (yes/no)
  • Time to complete
  • Number of errors or wrong paths
  • Assistance requests
  • Self-reported difficulty (1-5 scale)

Observation Guide

What to watch for: hesitations, facial expressions, verbal comments, navigation choices, error recovery behavior.

Task Types

  • **Exploratory**: Find information (e.g., 'Find the return policy')
  • **Specific**: Complete a goal (e.g., 'Add a blue shirt size M to your cart')
  • **Comparative**: Choose between options
  • **Open-ended**: Achieve a goal with multiple valid paths

Scenario Writing Rules

  • Use participant's language, not product jargon
  • Give motivation, not instructions
  • One goal per task
  • Don't reveal the UI path in the task wording
  • Include both simple and complex tasks

Best Practices

  • Pilot test your scenarios before real sessions
  • Order tasks from easy to hard
  • Include a warm-up task
  • Prepare follow-up questions per task
  • Write more scenarios than you need (allow flexibility)
Read more
Ships withdesigner-skills

Design skills for the agent era, written so an AI agent can actually use them. 273 skills and 76 commands across 33 plugins, in five collections, for Claude Code and Gemini CLI. Not sure which skill you need?

Get the whole plugin

Other skills on designer-skills.