mcpField
T
test-scenario

test-scenario

github.com/owl-listenerTesting & quality3.1k2.1k installsUpdated 8w ago
Repository

About test-scenario

A skill for UX researchers to write usability test scenarios with realistic tasks, measurable success criteria, and observation guidance. It covers several task styles and recommends a progression from warm-up to harder tasks.

Key features

  1. 01Realistic, goal-oriented test tasks
  2. 02Measurable completion criteria
  3. 03Structured participant observation
  4. 04Exploratory, specific, comparative, and open-ended task types
  5. 05Guidance on task order and pilot testing

Use cases

  1. 01Preparing usability sessions for a product
  2. 02Measuring task completion, errors, and difficulty
  3. 03Observing participant navigation and recovery

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/owl-listener/designer-skills --skill test-scenario

After installing, type/test-scenarioin Claude Code to confirm it loaded.

Details

From the project README

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)

Comments

Markdown supported