Research Planner
by @nkz55
Designs market and user research plans focused on methodology selection and research material authoring (screeners, surveys, interview guides, usability task...
clawhub install research-plannerπ About This Skill
name: research-planner description: > Designs market and user research plans focused on methodology selection and research material authoring (screeners, surveys, interview guides, usability task scripts, etc.). Use this skill whenever the user wants to plan or structure research activities, choose between qualitative and quantitative methods, or draft research artifacts, but not to analyze collected data.
Installation
Via Clawdhub:clawdhub install research-planner
Manual Installation:
npx skills add https://github.com/NKZ55/research-planner/tree/main/skills/research-planner
Research Planner
Market and user research planning skill focused on research design and documentation, not on data analysis.
This skill is inspired by systematic frameworks from:
This skill helps the agent:
Data analysis (qualitative coding, statistical analysis, report writing) is explicitly out of scope and should be delegated to analysis-focused skills (for example, interview-analysis skills such as Interview Analyst).
Scope
Phase Model
Use this phase model for every project. This skill covers only the planning and documentation phases.
Problem framing
β
Research strategy & method selection
β
Study plan & logistics
β
Research materials (screeners, guides, surveys, scripts)
β
Fieldwork / data collection [OUT OF SCOPE]
β
Analysis & reporting [OUT OF SCOPE β use analysis skills]
How to Use This Skill
For each user request:
1. Clarify the research need 2. Choose appropriate research approach(es) 3. Turn the approach into a concrete study plan 4. Generate the necessary research materials 5. Package everything into an execution-ready bundle
Always keep analysis out of scope and gently point users to analysis skills once data is collected.
Step 1: Clarify the Research Need
Before suggesting methods, derive a clear, consulting-style problem framing.
Output for this step:
Step 2: Choose Research Approach(es)
Use a small set of canonical user and market research methods. Combine methods when appropriate (mixed methods).
Method-Selection Matrix
| Primary goal | Typical method(s) | Notes | |----------------------------------------|---------------------------------------------------------|-------| | Explore unknown problem space | 1:1 in-depth interviews, contextual inquiry, diary | Discovery / generative research | | Evaluate usability of an experience | Moderated usability tests, unmoderated remote tests | Task-based, scenario-driven | | Measure attitudes or behaviors at scale| Structured survey, poll, simple experiment | Requires clear constructs and metrics | | Compare concepts or ideas | Concept testing sessions, preference tests, card sorts | May combine with interview or survey | | Understand real-world context | Field visits, observation, shadowing, diary study | Higher logistics cost |
Method choice should balance:
When recommending methods:
Step 3: Turn the Approach into a Study Plan
Following both classic marketing-research texts and NN/g research-plan guidance, every study plan should cover at least:
When the user asks for a plan, structure your answer in these sections and keep wording concise enough that it can be copy-pasted into a research plan document.
Step 4: Generate Research Materials
For each chosen method, generate concrete artifacts. Keep templates modular so they can be reused across projects.
4.1 Recruitment Screener
Structure:
Make the screener:
4.2 Participant Invitation & Consent Wording
Include:
Ensure consent text is non-legalistic but clear; defer to the userβs legal or compliance team for final approval.
4.3 Interview / Discussion Guide
For qualitative interviews, base structure on best practices from interview-focused texts:
Organize the guide as:
4.4 Usability Test Script
Components:
Include simple moderator cues (what to read verbatim, when to stay silent, when to probe).
4.5 Survey Questionnaire
When planning surveys, follow quantitative UX and survey-design guidance:
Output:
Step 5: Package an Execution-Ready Output
Default response format for this skill:
# Research Plan Overview1. Background & Objectives
[Problem statement, context, objectives]2. Research Approach
Primary method(s): [...]
Secondary method(s): [...]
Rationale: [...] 3. Participants
Target: [...]
Inclusion / exclusion: [...]
Sample size and rationale: [...] 4. Procedure & Timeline
[Study phases, session format, key milestones]5. Risks & Ethics
[Key ethical considerations, data handling notes]6. Research Materials
Recruitment screener
Invitation & consent text
Interview / test script / survey questions
Populate each section with concrete, copy-paste-ready content tailored to the userβs situation.
Phases Overview
For more detailed step-by-step guidance, this skill includes phase files under phases/:
phases/01-clarify-need.mdphases/02-method-selection-and-plan.mdphases/03-materials-and-logistics.mdWhen a user task is complex (e.g., multi-method study, multiple stakeholders, long timeline), prefer:
1. Following the relevant phases/ file(s) for process and structure.
2. Using the templates/ files for concrete artifact formats.
Templates Overview
This skill is bundled with detailed templates under templates/. Use them as follows:
templates/research-plan-template.md
- When the user needs stakeholder alignment or a kickoff agenda, read:
- templates/stakeholder-kickoff-template.md
- templates/stakeholder-walkthrough-template.md
- When scoping what is out of scope and defining future research needs, read:
- templates/out-of-scope-and-research-needs-template.md
- When grounding a study in existing knowledge with a desk/literature review, read:
- templates/literature-review-template.mdtemplates/uxr-consent-form-template.mdtemplates/interview-guide-template.md
- For focus groups, read:
- templates/focus-group-template.md
- For persona workshops and persona documentation, read:
- templates/persona-workshop-and-template.md
- For stakeholder discovery sessions, read:
- templates/stakeholder-walkthrough-template.md
- For brainstorming/ideation sessions, read:
- templates/brainstorming-template.mdtemplates/usability-test-script-template.md
- For expert reviews of flows or UI, read:
- templates/expert-review-template.md
- For heuristic evaluations, read:
- templates/heuristic-evaluation-template.md
- For rapid iterative testing (RITE), read:
- templates/rapid-iterative-testing-rite-template.md
- For eye-tracking studies, read:
- templates/eye-tracking-template.md
- For A/B tests / online experiments, read:
- templates/ab-test-template.mdtemplates/card-sorting-template.md
- For tree testing (validating IA structure), read:
- templates/tree-testing-template.mdtemplates/customer-satisfaction-surveys-template.md
- For recruitment screeners and survey structures, read:
- templates/screener-and-survey-template.mdtemplates/contextual-inquiry-template.md
- For diary studies, read:
- templates/diary-study-template.md
- For shadowing and associated note-taking, read:
- templates/shadowing-template.md
- templates/shadowing-notes-template.md
- For ethnographic or deep contextual work, read:
- templates/ethnography-template.mdtemplates/jobs-to-be-done-template.md
- For gap analyses (current vs desired experience or capability), read:
- templates/gap-analysis-template.md
- For user journeys / experience maps, read:
- templates/journey-map-template.md
- For competitive or comparative analysis, read:
- templates/competitive-analysis-template.md
- For Kano analysis of feature satisfaction, read:
- templates/kano-analysis-template.mdtemplates/empathy-map-template.md
- For storyboards to visualize key moments, read:
- templates/storyboard-template.mdWhen generating any concrete artifact (plan, screener, guide, script, survey, etc.), first:
1. Identify the relevant method(s) based on the userβs goal.
2. Read the corresponding template file(s) from templates/.
3. Adapt the structure and fill in project-specific details.
Future Extensions
To keep SKILL.md concise, move heavier content into separate files when needed:
phases/ directory for more detailed, phase-by-phase instructions (similar to interview-analysis skills)templates/ for long-form templates and examplesLink to those files from this skill when they exist, and keep this core document focused on the high-level framework and standard response structures.