skills.rest
tarunccet
tarunccetCOMMUNITY
Explore all skills by this author →
GitHub

problem-statement

Synthesize qualitative and quantitative inputs into evidence-based problem statements.

5|2|Updated Mar 27, 2026
Search Tags:#root-cause-analysis#stakeholder-alignment#evidence-synthesis#product-discovery#success-criteria#problem-statement
One-click install
npx skills add https://github.com/tarunccet/pm-skills --skill problem-statement-tarunccet
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: problem-statement
Source: https://github.com/tarunccet/pm-skills/tree/main/pm-product-discovery/skills/problem-statement
Command: npx skills add https://github.com/tarunccet/pm-skills --skill problem-statement-tarunccet

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Aligns teams around a clear, evidence-based definition of the problem before jumping to solutions, preventing wasted effort on features that don't address root causes. It turns scattered observations, anecdotal claims, and partial data into a structured, actionable problem statement that guides discovery and prioritization.

Core Features & Use Cases

  • Structured Problem Output: Produces a one-sentence problem plus sections for user segment, current behavior, pain points, business impact, evidence, root-cause analysis, success criteria, and anti-scope.
  • Evidence Evaluation: Synthesizes analytics, interview notes, survey results, and support tickets and rates evidence strength as Strong/Moderate/Weak.
  • Root Cause Analysis: Runs a 5 Whys chain to surface potential root causes and clarifies the difference between symptoms and causes.
  • Use Case: Use this skill to align stakeholders before writing a PRD, to scope discovery work, or to stop teams from proposing solutions without validated problems.

Quick Start

Ask the skill to write a problem statement for users abandoning onboarding at step 3, including user segment, current behavior, evidence, impact, root-cause analysis, and success criteria.

Frequently Asked Questions about problem-statement

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

FAQPage Schema
How do I write an evidence-based problem statement for product discovery?▼

An evidence-based problem statement synthesizes qualitative and quantitative inputs to define user segments, current behavior, business impact, and success criteria. It applies a five-whys root-cause analysis to transform scattered observations into a scoped, solution-agnostic sentence.

What is the best way to align stakeholders before writing a PRD?▼

Align stakeholders before writing a PRD by generating a structured problem statement that clarifies pain points, evidence strength, and anti-scope. This prevents teams from jumping to solutions without validated problems and scopes downstream discovery work.

How do I synthesize interview transcripts and analytics into a root-cause analysis?▼

Synthesize interview transcripts and analytics by running a 5 Whys chain to surface potential root causes and separate symptoms from actual issues. The process evaluates evidence strength as Strong, Moderate, or Weak to validate the identified root causes.

Can I use support tickets and survey results to define success criteria for a product?▼

Support tickets and survey results can be synthesized to define clear success criteria within a structured problem statement. The output scopes discovery work by rating the evidence strength of these inputs and defining the boundaries of the product solution.

When do I need a solution-agnostic problem statement for stakeholder alignment?▼

You need a solution-agnostic problem statement when teams risk wasting effort on features that do not address root causes. It aligns stakeholders around a validated problem definition using synthesized observations, analytics, and strategic goals before scoping begins.

Related Skills

Explore More Product & Management Skills→
ilove323ilove323

synthesize-research

Synthesize user research inputs into prioritized findings with evidence and recommendations.

Community
Intermediate
Kushal9889Kushal9889

to-prd

Synthesize a Product Requirements Document from conversation context using a structured template.

Community
Intermediate
harrymunroharrymunro
1

prd

Generate a structured PRD with goals, user stories, and success metrics.

Community
Advanced
curiositechcuriositech
10

dag-failure-analyzer

Analyze DAG execution failures to identify root causes and remediation guidance.

Official
Advanced