write-task-scenarios

Converts research goals into unbiased usability-test task scenarios using NN/g's 7-step method.

1|Updated Jul 13, 2026
One-click install
npx skills add https://github.com/dineshrevunuru/SuperSkills --skill write-task-scenarios-dineshrevunuru
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: write-task-scenarios
Source: https://github.com/dineshrevunuru/SuperSkills/tree/main/write-task-scenarios
Command: npx skills add https://github.com/dineshrevunuru/SuperSkills --skill write-task-scenarios-dineshrevunuru

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Usability tests fail when task wording leaks the answer — leading phrasing, interface echo, or compound tasks produce "everyone succeeded" non-findings. This Skill turns research goals into realistic, unbiased task scenarios participants can actually perform. ## Core Features & Use Cases - 7-step goal-to-scenario chain: Traces every task from research goal through research question, user goal, and activity to a participant-facing scenario, keeping the full chain auditable. - 10-mistake lint pass: Checks every task against the classic task-writing failures — interface echo, embedded steps, hypothetical phrasing, compound tasks, missing data, feature priming, and more. - Quant vs qual forking: Adapts each task for quantitative studies (binary success states, identical wording) or qualitative studies (open-ended exploration, observation notes). - Use Case: You have a PRD for a new booking flow and a planned usability test. Use this Skill to convert the research questions into five participant task scenarios, lint them against the live interface, and produce a traceability table plus participant-facing cards. ## Quick Start Use the write-task-scenarios skill to draft and lint usability test tasks for our new checkout flow study.

Frequently Asked Questions about write-task-scenarios

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write task scenarios for a usability test?

Start from the research goal, derive answerable research questions, identify the user goal behind each, pick the activity, then draft a short scenario with context, motivation, and an actionable ask. Supply any data the participant needs and lint every task before piloting.

What are the most common usability task writing mistakes?

The top mistakes are interface echo (task words matching UI labels), embedded steps that narrate the route, hypothetical phrasing, compound tasks, missing data, and feature priming. Each one leaks the answer or confounds the result, so lint every task against all ten before the pilot.

What is the difference between quantitative and qualitative usability tasks?

Quantitative tasks need one binary, predefined success state, identical wording for all participants, and concrete targets so metrics like success rate and time-on-task are valid. Qualitative tasks can be open-ended and exploratory, with flexible wording and observation notes for the moderator.

When should I not use task scenarios in user research?

Do not use task scenarios for interview questions participants answer rather than perform — that belongs to an interview guide. Study goals, sample size, mode selection, and pilot protocol belong to overall test planning, and tree-test tasks belong to information architecture work.

Why do all participants succeed in my usability test?

Universal success usually means the tasks leaked the answers through interface echo, embedded steps, or feature priming. Re-lint the tasks against the live interface, checking that no task word matches a nav label, button, or heading on the path.