Menu

Individual skill

usability-test-plan

0upvotes

Plans a usability study - research questions, realistic task scenarios with success criteria, metrics (completion rate, time on task, SEQ, SUS), a recruiting screener, and moderated vs. unmoderated guidance. Use when someone says "plan a usability test", "write task scenarios for our prototype", "how many participants do we need", or is about to put an interface or prototype in front of users. Do NOT use for open-ended discovery interview guides - use interview-guide-builder instead; for analyzing quantitative A/B experiments, use ab-test-analyzer.

skills/usability-test-plan/SKILL.md

Read pinned source

Source commit 97a13607d669157a4a16d5ba79b77f208319f7b9

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Not checked yet
Last checked
Nov 6, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
24
Repository last updated
Oct 13, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Usability Test Plan

A test plan is the contract between the research question and the study execution. Without one, teams run sessions, gather impressions, and call it usability testing. With one, findings are defensible and actionable.

## Define the Research Questions First

Before writing tasks, state 2-4 specific research questions the test must answer. Examples: 'Can users complete onboarding without assistance?', 'Do users understand the permission model before granting access?'. Tasks flow from questions - not the other way around. Reject any task that does not map to a research question.

## Writing Task Scenarios

Task scenarios must be realistic, motivated, and free of interface terminology. Good: 'You need to share the monthly report with your manager so she can review it before the board meeting. Please show me how you would do that.' Bad: 'Use the Share button to export the document.' Give participants context and a goal, not instructions. Each task should have a clear end state the observer can recognize.

## Success Criteria and Metrics
Back to top