
Test Scenario
Turns test scenarios into actual tasks people can complete without being led to the answer. You get context setting that motivates without hinting, success criteria you can measure (time, errors, completion rate), and observation guides for what to watch. It pushes you away from asking questions and toward action-oriented goals, which is the difference between "How would you find the return policy?" and "Find the return policy." Includes task types from exploratory to open-ended and rules like no product jargon, one goal per task, and ordering easy to hard. Honestly most useful if you're running usability tests and keep accidentally writing tasks that telegraph the UI solution.
- skills.sh installs
- 2.3K
- GitHub stars
- 3.3K
- last updated
- Aug 21, 2026
Install
$ npx -y skills add owl-listener/designer-skills --skill test-scenario --agent claude-codeInstalls into .claude/skills of the current project.
Files
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
Sponsors
Details
- Repository
- github.com/owl-listener/designer-skills
- Category
- Testing & QA
- First seen
- Jun 3, 2026
More from owl-listener/designer-skills
All 68- Design Review Process2.3K
- North Star Vision2.3K
- Opportunity Framework2.3K
- Summarize Interview2.2K
- Design System Adoption2.2K
- Team Workflow2.2K
- Design Sprint Plan2.2K
- Click Test Plan2.2K
- Version Control Strategy2.2K
- Information Architecture2.2K
- Aesthetic Usability2.2K
- Navigation Patterns2.1K
- Motion System2.1K
- Service Blueprint2K
- Presentation Deck3.4K
- Typography Scale2.8K
- Illustration Style2.8K
- Visual Hierarchy2.8K
- Color System2.7K
- Dark Mode Design2.7K
- User Flow Diagram2.7K
- Icon System2.6K
- Layout Grid2.6K
- Heuristic Evaluation2.6K