usability-test-plan
This Claude Code skill generates comprehensive usability test plans for evaluating designs and prototypes. Use it when preparing moderated or unmoderated testing sessions to establish research questions, participant screening criteria, task scenarios with success metrics, facilitation scripts, data collection methods, and analysis frameworks that guide systematic evaluation of user experience.
git clone --depth 1 https://github.com/Owl-Listener/designer-skills /tmp/usability-test-plan && cp -r /tmp/usability-test-plan/design-research/skills/usability-test-plan ~/.claude/skills/usability-test-planSKILL.md
# Usability Test Plan Design a comprehensive usability test plan for evaluating designs and prototypes. ## Context You are a senior UX researcher designing a usability test plan for $ARGUMENTS. If the user provides files (prototypes, designs, personas), read them first. ## Instructions 1. **Define objectives**: What specific questions should this test answer? 2. **Create the test plan** with: - **Research questions**: 3-5 specific questions to answer - **Methodology**: Moderated vs unmoderated, remote vs in-person, think-aloud protocol - **Participants**: Screening criteria, sample size (5-8 per segment), recruitment approach - **Tasks**: 5-8 realistic task scenarios with success criteria and expected completion time - **Metrics**: Task success rate, time on task, error rate, SUS/SEQ scores, satisfaction rating - **Facilitation guide**: Script for introduction, task delivery, probing, and debrief - **Data collection**: What to record, observation template, note-taking framework - **Analysis plan**: How findings will be synthesized and prioritized 3. **Include a pilot test checklist**: What to verify before the real sessions. 4. Think step by step. Present in a ready-to-use format. ## Further Reading - Rocket Surgery Made Easy — Steve Krug - Measuring the User Experience — Tom Tullis and Bill Albert
Facilitate a structured team critique — framing, feedback rules, and actionable outcomes. Use when running a session with people in the room. For a solo expert review, use `heuristic-evaluation` (prototyping-testing).
Inventory and prioritise accumulated design inconsistencies across a product. Use when drift has built up over time. For token coverage specifically use `design-token-audit` (designer-toolkit); for WCAG gaps use `accessibility-audit` (design-systems).
Communicate design's contribution to business and user outcomes in stakeholder language. Use when reporting results upward. For choosing the metrics in the first place, use `metrics-definition` (ux-strategy).
Build a QA checklist for verifying that a build matches the design. Use at implementation review. For the spec engineers build from, use `handoff-spec`.
Establish review gates — criteria, checkpoints, and approval flow. Use when work ships without consistent review. For running one individual session, use `design-critique`.
Plan and facilitate a design sprint from challenge framing through prototype testing. Use when compressing discovery into days. For ongoing team cadence, use `team-workflow`.
Write the implementation handoff — measurements, behaviours, assets, states, and edge cases. Use when engineering picks up the work. For verifying the result afterwards use `design-qa-checklist`; for reusable library components use `component-spec` (design-systems).
Design the team's operating rhythm — task management, collaboration rituals, and tooling. Use when the day-to-day cadence needs structure. For a time-boxed sprint, use `design-sprint-plan`.