Test Scenario
Write usability test scenarios with tasks, success criteria, and observation guides.
Install
/plugin marketplace add sethdford/claude-skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add sethdford/claude-skills --skill test-scenariogit clone --depth 1 https://github.com/sethdford/claude-skills.git /tmp/claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills/designer/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
- sethdford/claude-skills
- Path
designer/prototyping-testing/skills/test-scenario/SKILL.md- License
- MIT
- Repo updated
- 11 March 2026
FAQ
What does the Test Scenario skill do?
Write usability test scenarios with tasks, success criteria, and observation guides.
How do I install the Test Scenario skill?
Claude Code plugin: /plugin marketplace add sethdford/claude-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 sethdford/claude-skills, which has 48 GitHub stars and 10 forks.
Related skills
A B Test Design
48sethdford/claude-skills
Design rigorous A/B tests with hypotheses, variants, metrics, and sample size calculations.
A B Test Design Pm
48sethdford/claude-skills
Analytics and experimentation skill for product managers.
Abuse Case Design
48sethdford/claude-skills
Design abuse cases (negative use cases) showing how attackers misuse system features. Use when identifying attacks that exploit intended functionality or business logic flaws.
Test Strategy
48sethdford/claude-skills
Create testing pyramid with unit/integration/E2E strategy. Define coverage targets and high-risk testing. Use when planning tests for features.
Test Pyramid Design
48sethdford/claude-skills
Design test pyramid architecture balancing unit, integration, and E2E tests. Use when establishing test level distribution and automation strategy.
Test Strategy Design
48sethdford/claude-skills
Design comprehensive test strategies aligned with project goals, risks, and constraints. Use when planning testing efforts for new projects or major releases.
Browse the most popular Claude skills, all testing & qa skills, or write your own with the skills generator.