write-problem-statement

Writes solution-free problem statements and derives scoped, timeboxed discovery plans from them.

1|Updated Jul 13, 2026
One-click install
npx skills add https://github.com/dineshrevunuru/SuperSkills --skill write-problem-statement-dineshrevunuru
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: write-problem-statement
Source: https://github.com/dineshrevunuru/SuperSkills/tree/main/write-problem-statement
Command: npx skills add https://github.com/dineshrevunuru/SuperSkills --skill write-problem-statement-dineshrevunuru

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Projects often start from a stakeholder's solution ("build a chatbot", "redesign the homepage") with no agreed statement of the underlying problem, leading to unbounded discovery, scope creep, and research that enables no decision. This Skill gates every project kickoff by producing one solution-free problem statement plus a scoped, timeboxed discovery plan. ## Core Features & Use Cases - Solution-to-problem laddering: Captures the raw ask verbatim, parks every solution idea in an attributed Icebox, and ladders up with "what does that solve, for whom, and how do we know?" until an observable problem is found. - Evidence audit and lint checklist: Labels the statement Evidenced or Hypothesis (under-evidenced), then enforces a checklist covering single-problem focus, zero solution words, named user segment, and a Goldilocks altitude test. - Discovery scoping: Derives 2-4 discovery goals, 3-5 team-facing research questions, a timebox with end date, an exit decision, and out-of-scope lists; optionally maps product seams when the statement feeds a build spec. - Use Case: A salon owner asks for an AI chatbot. The Skill iceboxes the chatbot, ladders to the real problem (prospective clients can't reach anyone by phone during service hours), flags the missed-call estimate as under-evidenced, and outputs a two-week discovery plan with a go/no-go exit decision. ## Quick Start Ask the AI to write a problem statement and scoped discovery plan for your project kickoff, starting from the stakeholder's raw request.

Frequently Asked Questions about write-problem-statement

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

FAQPage Schema
How do I write a problem statement for a UX project?

Answer the 5 Ws (who, what, where, when, why), then compress to 2-4 sentences naming the affected segment, the gap between current and desired state, evidence status, and the consequence of doing nothing. The statement must contain zero solution words and pass a lint checklist before discovery begins.

What should I do when a stakeholder asks for a specific solution?

Park the solution verbatim in an Icebox with attribution, then ladder up by asking "what does that solve, for whom, and how do we know?" until you reach an observable problem. The iceboxed solution re-enters at ideation on equal footing with whatever discovery surfaces.

What is the difference between a problem statement and a research question?

A problem statement names one solution-free problem before research begins; research questions are team-facing unknowns derived from it that discovery must answer. Research questions are not interview questions — translating them into participant-facing guides belongs to the research-plan step.

When should I not use a problem statement skill?

Skip it when you already have research data and need need-statements or How-Might-We questions (those are Define-stage outputs), when you need a full research plan with methods and participants, or when you are still deciding which business problem deserves attention.

How long should a discovery phase be timeboxed?

Set an end date before starting: 1-2 weeks for a known product and single feature area, 3-6 weeks for a new problem space or user segment. At the deadline, decide with what you have or explicitly re-scope rather than silently extending.