Agent skill

UX Research Plan

by mohitagw15856 in mohitagw15856/pm-claude-skills

Create a structured UX research plan for any product question or feature.

MITAuto-check passedFrontend & Design

Install UX Research Plan

skills CLI
$ npx skills add mohitagw15856/pm-claude-skills --skill ux-research-plan -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install mohitagw15856/pm-claude-skills ux-research-plan --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/ux-research-plan .claude/skills/ux-research-plan && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
ux-research-plan
GitHub stars
1.4k
Token cost
~1.6k tokens
SKILL.md length
794 words
Files
1
Skills in repo
1,348
Repo updated
First seen
Licence
MIT

At a glance

Create a structured UX research plan for any product question or feature.

  • Works in 6 steps: Research Objectives → Research Questions → Methodology & Rationale → …
  • Asked to write a research plan
  • SKILL.md covers Required Inputs, Output Structure, 1. Research Objectives and 2. Research Questions, plus 7 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

UX Research Plan is an agent skill from mohitagw15856/pm-claude-skills. Create a structured UX research plan for any product question or feature. Use when asked to write a research plan, design a user study, create a discussion guide, write screener questions, or plan usability testing. Produces a full research plan with objectives, methodology, screener, discussion guide, and synthesis framework.

Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Frontend & Design, covering UX design and User research. The repository describes itself as: 1255 professional Agent Skills for Claude, ChatGPT, Gemini, Cursor & Codex — PRDs, postmortems, leases, medical bills, layoffs, go-bags, new countries. Plain markdown, MIT, in… The licence is MIT.

When your agent uses it

  • Asked to write a research plan
  • Design a user study
  • Create a discussion guide
  • Write screener questions

Example prompts

  • “/ux-research-plan”

Workflow steps

6 steps, taken from the step headings in SKILL.md.

  1. Research Objectives
  2. Research Questions
  3. Methodology & Rationale
  4. Participant Screener
  5. Discussion Guide
  6. Synthesis Framework

What it can do on your machine

Read from SKILL.md and the folder at commit 1cbf1f0. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

UX Research Plan loads about 1.6k tokens when it runs. Until then it costs about 86 tokens; SKILL.md has 794 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~86
When it runs · the whole SKILL.md, loaded when a task matches
~1.6k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from mohitagw15856/pm-claude-skills at commit 1cbf1f0, republished under its MIT licence (© mohitagw15856). 794 words, ~1,587 tokens.

Download SKILL.mdSave it as .claude/skills/ux-research-plan/SKILL.md (or your agent's skills folder).
name
ux-research-plan
description
Create a structured UX research plan for any product question or feature. Use when asked to write a research plan, design a user study, create a discussion guide, write screener questions, or plan usability testing. Produces a full research plan with objectives, methodology, screener, discussion guide, and synthesis framework.

UX Research Plan Skill

This skill creates a complete, ready-to-execute UX research plan. Output covers everything from research objectives to screener questions, discussion guide, and synthesis framework.

Required Inputs

Ask the user for these if not provided:

  • Research question (what decision will this research inform?)
  • Product area or feature being researched
  • Research type (Generative / Evaluative / Usability testing / Diary study / Survey)
  • Stage (Discovery / Concept validation / Prototype testing / Live product)
  • Target participants (role, demographics, behaviour — who should we talk to?)
  • Timeline and number of sessions
  • Existing assumptions or hypotheses (optional but valuable)

Output Structure


UX Research Plan: [Study Title]

Product area: [Area] Research type: [Type] Date: [Timeline] Researcher: [Leave for user]


1. Research Objectives

State 2–4 clear research objectives. Each objective should map to a decision that will be made differently depending on what you find.

Objective [N]: Understand [specific thing] so we can [decision this informs].


2. Research Questions

[5–8 questions — the actual questions you want research to answer. These are not the interview questions; they're the knowledge gaps. Organised under each objective.]

Objective 1:

  • RQ1.1: [Research question]
  • RQ1.2: [Research question]

3. Methodology & Rationale

Method chosen: [e.g. Semi-structured interviews / Usability testing / Concept testing]

Why this method: [2–3 sentences. Match method to research type. If evaluative: usability testing. If generative: contextual inquiry or interviews. If testing comprehension: 5-second test or concept test.]

What this method will and won't tell us:

  • Will tell us: [What this method is good at revealing]
  • Won't tell us: [What's out of scope — be honest about limits]

Sample size: [Recommended number of sessions and why — e.g. "5–6 moderated interviews for generative research; 5–8 usability sessions to identify top issues"]


4. Participant Screener

Recruitment criteria:

CriterionMust Have / Nice to HaveDisqualify if
[e.g. Uses project management software daily]Must Have[Never uses any PM tool]
[e.g. Works in a team of 5+]Must Have—
[e.g. B2B industry]Nice to Have—

Screener questions (5–8 questions):

[Q1] [Screening question — clear, not leading]

  • [Answer options — flag which qualify/disqualify]

[Q2] ...

Incentive recommendation: [Amount and format — e.g. "£50 gift voucher for a 60-min session is standard in the UK for professional participants"]


5. Discussion Guide

Structure the session:

Opening (5 min)
  • Introduce yourself and the study
  • "We're testing the design, not you — there are no wrong answers"
  • Permission to record
  • Warm-up: [1–2 easy questions to build rapport — e.g. "Tell me about your role and what a typical week looks like"]
Core Questions (by section)

Section [A]: [Topic] (~X min)

  1. [Open question — start broad] [Probe: Tell me more about...]
  2. [Follow-up to go deeper] [Probe: Can you walk me through what happened?]
  3. [Specific scenario or past behaviour question]

Section [B]: [Topic] (~X min) [Continue with 2–3 questions per section]

Usability tasks (if applicable):

"I'm going to ask you to try a few things with this prototype. Please think aloud as you go."

  • Task [N]: [Clear task instruction — write from the user's perspective, not "click on X" but "find where you would go to do Y"]
    • Success criteria: [What "completing this task" looks like]
    • What to observe: [Where friction typically appears]
Show full SKILL.md (286 more words)Show less
Closing (5 min)
  • "Is there anything about [topic] we haven't covered that you think is important?"
  • "If you could change one thing about [product/concept], what would it be?"
  • Debrief and thank

6. Synthesis Framework

After sessions, use this framework to synthesise findings:

Step 1: Session notes → Key observations For each session: 3–5 specific observations (behaviours, quotes, reactions — not interpretations yet)

Step 2: Affinity mapping Group observations by theme across all sessions. Aim for 4–7 clusters.

Step 3: Insight statements For each cluster: "When [context], users [behaviour/experience], because [underlying need or mental model]."

Step 4: Implications For each insight: "This means we should [design/product implication]" or "This challenges our assumption that [assumption]."

Step 5: Research report structure:

  • Key findings (3–5 headlines)
  • Supporting evidence per finding
  • Design recommendations
  • Open questions for next research cycle

Quality Checks

  • Research objectives map to real decisions
  • Discussion guide opens broad before going specific
  • Screener criteria are specific enough to get the right participants
  • Tasks (if usability) are written from the user's perspective
  • Synthesis framework is included
  • Incentive recommendation is included

Anti-Patterns

  • Do not write a research plan without clearly stated research objectives — every methodology choice must flow from the objectives
  • Do not design a plan that mixes generative and evaluative research without clearly separating them
  • Do not omit screener criteria — recruiting unqualified participants invalidates the research
  • Do not write discussion guide questions that are leading — questions must be neutral and open-ended
  • Do not skip the incentive recommendation — uncompensated research has lower participant quality and completion rates

Example Trigger Phrases

  • "Write a research plan for [feature or product area]"
  • "Create a discussion guide for user interviews about [topic]"
  • "Plan a usability test for [prototype or feature]"
  • "Write screener questions for [target user type]"

© mohitagw15856, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/ux-research-plan of mohitagw15856/pm-claude-skills.

Open the folder on GitHubat commit 1cbf1f0

Compare with similar skills

UX Research Plan next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

UX Research Plan compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
UX Research Plan this skillmohitagw15856/pm-claude-skills1.4k—~1.6kAutomated safety check: PassMIT
Prototypeplugin87/ux-ui-agent-skills1.6k—~614Automated safety check: PassMIT
Usability Frameworksslgoodrich/agents139—~3.5kAutomated safety check: PassCustom licence
Nova Act UsabilityLeoYeAI/openclaw-master-skills2.2k—~7.4kAutomated safety check: PassMIT
UX Linterrevfactory/harness-1001.3k—~1.1kAutomated safety check: PassApache-2.0
UX Heuristicasgard-ai-platform/skills242—~1.4kAutomated safety check: PassMIT

Similar skills

  • Prototype

    plugin87/ux-ui-agent-skills

    Move an idea up the fidelity ladder (content-first → wireframe → low-fi → high-fi → code) with a validation plan at each level, plus user-journey mapping and usability-testing scripts.

    1.6k GitHub stars~614 tokensUpdated 3 days ago
    Frontend & DesignAuto-check passed
  • Usability Frameworks

    slgoodrich/agents

    Usability testing methodology, Nielsen's heuristics, and usability metrics.

    139 GitHub stars~3.5k tokensUpdated 6 mo ago
    Frontend & DesignAuto-check passed
  • Nova Act Usability

    LeoYeAI/openclaw-master-skills

    AI-orchestrated usability testing using Amazon Nova Act. An agent skill from LeoYeAI/openclaw-master-skills.

    2.2k GitHub stars~7.4k tokensUpdated 2 mo ago
    Frontend & DesignAuto-check passed
  • UX Linter

    revfactory/harness-100

    Checklist and best practices for validating CLI tool user experience.

    1.3k GitHub stars~1.1k tokensUpdated 6 mo ago
    Frontend & DesignAuto-check passed
  • UX Heuristic

    asgard-ai-platform/skills

    Conduct heuristic evaluation of user interfaces using Nielsen's 10 usability principles.

    242 GitHub stars~1.4k tokensUpdated 4 mo ago
    Frontend & DesignAuto-check passed
  • UI UX Designer

    aiskillstore/marketplace

    Create interface designs, wireframes, and design systems. An agent skill from aiskillstore/marketplace.

    433 GitHub starsUsed in 7 repos~2.4k tokens
    Frontend & DesignAuto-check passed

More from mohitagw15856/pm-claude-skills

All 1,348 skills in this repo
  • Car Tco

    mohitagw15856/pm-claude-skills

    Compare the total cost of car ownership across buy-new, buy-used, lease, and keep-your-current-car — depreciation, insurance, maintenance ramp, and fuel over a real horizon, not just the monthly…

    1.4k GitHub stars~1.1k tokensUpdated 2 days ago
    Auto-check passed
  • Cs Health Scorecard

    mohitagw15856/pm-claude-skills

    Build a customer health scorecard for a specific account. An agent skill from mohitagw15856/pm-claude-skills.

    1.4k GitHub stars~2.4k tokensUpdated 2 days ago
    Auto-check passed
  • Exit Waterfall

    mohitagw15856/pm-claude-skills

    Compute who gets what at each exit price from a cap table — liquidation preferences, conversion points, and where the founders' share collapses.

    1.4k GitHub stars~1.1k tokensUpdated 2 days ago
    Auto-check passed
  • Feature Prioritisation

    mohitagw15856/pm-claude-skills

    Apply prioritisation frameworks (RICE, MoSCoW, Kano, ICE, Opportunity Scoring) to rank features and backlog items.

    1.4k GitHub stars~2k tokensUpdated 2 days ago
    Auto-check passed
  • Fire Number

    mohitagw15856/pm-claude-skills

    Compute a financial-independence (FIRE) target and years-to-reach with every assumption labeled as an assumption — plus a sensitivity table instead of a single false-precision answer.

    1.4k GitHub stars~1.1k tokensUpdated 2 days ago
    Auto-check passed
  • Freelance Rate

    mohitagw15856/pm-claude-skills

    Derive a freelance day/hourly rate backwards from target income, honest billable utilization, overhead, and the self-employment tax premium — the arithmetic that proves a rate is not salary÷2000.

    1.4k GitHub stars~1.2k tokensUpdated 2 days ago
    Auto-check passed

Questions about UX Research Plan

What does UX Research Plan do?

Create a structured UX research plan for any product question or feature. UX Research Plan is an agent skill from mohitagw15856/pm-claude-skills. Create a structured UX research plan for any product question or feature.

When should I use UX Research Plan?

UX Research Plan fits situations like: asked to write a research plan; design a user study; create a discussion guide; write screener questions.

How do I install UX Research Plan in Claude Code?

Run `npx skills add mohitagw15856/pm-claude-skills --skill ux-research-plan -a claude-code`. Or copy the skill folder (skills/ux-research-plan in mohitagw15856/pm-claude-skills) into .claude/skills/ux-research-plan in your project. Claude Code loads it when a task matches its description.

How do I install UX Research Plan in Codex?

Run `npx skills add mohitagw15856/pm-claude-skills --skill ux-research-plan -a codex`. Or copy the skill folder (skills/ux-research-plan in mohitagw15856/pm-claude-skills) into .agents/skills/ux-research-plan in your project. Codex loads it when a task matches its description.

Can I use UX Research Plan in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mohitagw15856/pm-claude-skills --skill ux-research-plan -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/ux-research-plan, .gemini/skills/ux-research-plan, .github/skills/ux-research-plan and .opencode/skills/ux-research-plan in your project.

What does UX Research Plan need to run?

SKILL.md names no scripts, command-line tools or credentials: UX Research Plan is instructions for the agent only.

Does UX Research Plan access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is UX Research Plan safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does UX Research Plan use?

UX Research Plan is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does UX Research Plan use?

About 1.6k tokens (SKILL.md is roughly 6.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to UX Research Plan?

Skills that share tags, products or a category with UX Research Plan: Prototype (plugin87/ux-ui-agent-skills, 1.6k stars), Usability Frameworks (slgoodrich/agents, 139 stars), Nova Act Usability (LeoYeAI/openclaw-master-skills, 2.2k stars) and UX Linter (revfactory/harness-100, 1.3k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains UX Research Plan?

mohitagw15856 (a GitHub user) maintains it in mohitagw15856/pm-claude-skills, which has 1,434 GitHub stars. The repository holds 1,348 skills in this directory. The repository was last updated on October 9, 2026.

Source: mohitagw15856/pm-claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.