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).
Install
/plugin marketplace add Owl-Listener/designer-skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add Owl-Listener/designer-skills --skill test-scenariogit clone --depth 1 https://github.com/Owl-Listener/designer-skills.git /tmp/designer-skills
mkdir -p ~/.claude/skills
cp -r /tmp/designer-skills/prototyping-testing/skills/test-scenario ~/.claude/skills/test-scenarioPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# 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)
Details
- Skill name
test-scenario- Repository
- Owl-Listener/designer-skills
- Path
prototyping-testing/skills/test-scenario/SKILL.md- License
- MIT
- Repo updated
- 5 September 2026
FAQ
What does the Test Scenario skill do?
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).
How do I install the Test Scenario skill?
Claude Code plugin: /plugin marketplace add Owl-Listener/designer-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Test Scenario popular?
It lives in Owl-Listener/designer-skills, which has 3,414 GitHub stars and 447 forks.
Related skills
A B Test Design
3.4kOwl-Listener/designer-skills
Design an A/B experiment — hypothesis, variants, primary metric, and sample size. Use when a change can be measured quantitatively at scale. For observing behaviour qualitatively, use `test-scenario`.
Accessibility Audit
3.4kOwl-Listener/designer-skills
Audit an existing interface against WCAG, producing findings with severity ratings and remediation steps. Use when you have a design or build to assess now. Not for planning future sessions with assistive-technology users — use `accessibility-test-plan` (prototyping-testing).
Accessibility Test Plan
3.4kOwl-Listener/designer-skills
Plan accessibility testing — assistive technologies, participant criteria, WCAG coverage, and session protocol. Use when scheduling testing with real AT users. Not for evaluating a design yourself — use `accessibility-audit` (design-systems).
Usability Test Plan
3.4kOwl-Listener/designer-skills
Design a usability study — research questions, methodology, participant criteria, metrics, and facilitation guide. Use when planning the study as a whole. For writing the task scenarios inside it, use `test-scenario` (prototyping-testing).
Survey Design
3.4kOwl-Listener/designer-skills
Design unbiased survey instruments — question wording, scales, and sampling — to measure attitudes at scale. Use when you need quantitative breadth. For behavioural experiments, use `a-b-test-design` (prototyping-testing).
User Flow Diagram
3.4kOwl-Listener/designer-skills
Diagram screen-level paths, decision points, and branch logic. Use when specifying how a feature is traversed. For the emotional end-to-end arc, use `journey-map` (design-research).
Browse the most popular Claude skills, all testing & qa skills, or write your own with the skills generator.