Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
owl-listener avatar

Research Planning

  • 11 installs
  • 233 repo stars
  • Updated June 23, 2026
  • owl-listener/designpowers

Helps with productivity & planning tasks during AI-assisted development.

About

research-planning is a Claude Code skill for productivity & planning. It helps developers move faster with AI-assisted coding.

  • research-planning
  • Productivity & Planning
  • AI-coding skill

Research Planning by the numbers

  • 11 all-time installs (skills.sh)
  • Ranked #2,172 of 3,273 Productivity & Planning skills by installs in the Skillselion catalog
  • Data as of Aug 1, 2026 (Skillselion catalog sync)
npx skills add https://github.com/owl-listener/designpowers --skill research-planning

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs11
repo stars233
Last updatedJune 23, 2026
Repositoryowl-listener/designpowers

What it does

Helps with productivity & planning tasks during AI-assisted development.

Files

SKILL.mdMarkdownGitHub ↗

Research Planning

Research is how we replace assumptions with evidence. This skill structures what you need to learn before committing to a design direction.

When to Use

  • The design brief identifies unknowns about users, context, or behaviour
  • The team is making decisions based on assumptions rather than evidence
  • A design is being created for a new audience or unfamiliar context
  • Stakeholders disagree about user needs

Process

Step 1: Identify Knowledge Gaps

Review the design brief and list:

  • What do we know about the people who will use this? (Evidence-backed)
  • What do we assume? (Believed but unverified)
  • What do we not know? (Acknowledged gaps)

Present this to the user. Assumptions and unknowns become research questions.

Step 2: Frame Research Questions

Convert gaps into answerable questions. Good research questions are:

  • Specific — "How do users with screen readers navigate multi-step forms?" not "Is the form accessible?"
  • Observable — focused on behaviour, not opinion
  • Actionable — the answer will change a design decision

Aim for 3-5 research questions. More than that means you need to narrow scope.

Step 3: Select Methods

Match methods to questions:

Question TypeRecommended Methods
"What do people currently do?"Journey mapping, diary studies, contextual inquiry
"Why do people struggle with X?"Usability testing, think-aloud protocols
"What do people need?"Interviews, jobs-to-be-done analysis
"Which approach works better?"A/B testing, preference testing, card sorting
"How does our offering compare?"Competitive analysis, heuristic evaluation
"Who are we designing for?"Persona development, ability spectrum mapping

Step 4: Plan for Inclusion

Every research plan must address:

  • Participant diversity — include people with disabilities, different ages, different technical literacy, different languages
  • Method accessibility — ensure research methods themselves are accessible (e.g., interview formats that work for people with communication differences)
  • Situational contexts — include scenarios of stress, distraction, low bandwidth, unfamiliar environments

Step 5: Write the Research Plan

# Research Plan: [Topic]

## Research Questions
1. [Question]
2. [Question]
3. [Question]

## Methods
| Method | Questions Addressed | Participants | Timeline |
|--------|-------------------|-------------|----------|
| [Method] | Q1, Q2 | [Who and how many] | [When] |

## Inclusion Considerations
[How participant diversity and method accessibility will be ensured]

## Expected Outputs
[What deliverables this research will produce — personas, journey maps, findings report]

## Decision Points
[Which design decisions this research will inform]

Save to: docs/designpowers/research/YYYY-MM-DD-<topic>-plan.md

Step 6: User Review

Present the plan. Confirm scope, methods, and timeline are realistic.

Integration

  • Called by: design-discovery
  • Calls: inclusive-personas (when persona development is a research output)
  • Pairs with: design-strategy (research informs strategy)

What This Skill Does NOT Do

This skill plans research — it does not execute it. Execution happens with real people in the real world. The plan ensures that when research happens, it is structured, inclusive, and actionable.

Related skills

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.