usability-test-plan
Design a usability test plan with tasks, success metrics, participant criteria, and facilitation guide. Use when planning moderated or unmoderated usability testing sessions.
npx skills add Owl-Listener/designer-skills --skill usability-test-plan --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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.
- Context
- Instructions
- Further Reading
What does the usability-test-plan skill do?
Design a usability test plan with tasks, success metrics, participant criteria, and facilitation guide. Use when planning moderated or unmoderated usability testing sessions.
How do I install it?
Run `npx skills add Owl-Listener/designer-skills --skill usability-test-plan --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From Owl-Listener/designer-skills, a repository with 1,964 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.