product-design-research

Researches user pain points and UX friction for a named product from public and internal sources.

634|124|Updated Feb 10, 2026
One-click install
npx skills add https://github.com/AIDotNet/OpenCowork --skill product-design-research
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: product-design-research
Source: https://github.com/AIDotNet/OpenCowork/tree/main/resources/extensions/product-design/skills/product-design-research
Command: npx skills add https://github.com/AIDotNet/OpenCowork --skill product-design-research

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Product teams often lack a clear, evidence-backed picture of what users actually struggle with. This Skill runs a structured UX research scan across public communities and internal tools to surface the highest-signal user problems for a specified product.

Core Features & Use Cases

  • Multi-source evidence gathering: Searches Reddit, X/Twitter, Hacker News, Stack Overflow, GitHub issues, forums, and reviews, plus internal sources like Slack, Gong, Notion, Linear/Jira, and support notes when connectors are available.
  • Ranked problem clustering: Groups evidence into categories such as onboarding friction, docs/help issues, developer experience, billing friction, and reliability, then ranks by severity, frequency, confidence, and product leverage.
  • Cited research brief: Produces an executive read, ranked UX problems with evidence and recommended product moves, a source map, and an opportunity map split into fix-this-week, fix-this-quarter, and needs-deeper-research.
  • Use Case: Ask it to research onboarding complaints for a SaaS product, and receive a cited brief separating loud anecdotes from frequent problems with concrete recommended actions.

Quick Start

Research the top current user complaints and UX friction for the product Linear and give me a ranked research brief with sources.

Frequently Asked Questions about product-design-research

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

FAQPage Schema
How do I research user pain points for a product?

Specify the product name and this Skill scans public sources like Reddit, Hacker News, Stack Overflow, and GitHub issues, plus internal tools when available. It clusters evidence into ranked UX problems with citations, severity, and recommended product moves.

What sources does UX research cover for product complaints?

Public sources include Reddit, X/Twitter, Hacker News, Stack Overflow, GitHub issues and discussions, forums, blogs, reviews, and YouTube comments. Internal sources such as Slack, Gong, Notion, Linear/Jira, and support notes are used when connectors are available.

Can I use internal company data for UX research?

Yes, internal sources like Slack, Gong, Notion, Google Drive, Linear/Jira, and CRM notes are searched when connectors are available and the request allows it. Internal-only evidence is marked separately from public evidence in the output.

What output format does the product research brief use?

The default output is an in-chat research brief with an executive read, ranked UX problems with evidence and severity, a source map showing what was searched, and an opportunity map grouped into fix this week, fix this quarter, and needs deeper research.

How does it avoid overclaiming from anecdotal complaints?

The Skill separates observed evidence from inference, distinguishes loud complaints from frequent problems, and assigns confidence levels to each ranked issue. It explicitly states when source access is missing or weak rather than filling gaps with speculation.