AI Skills for Problem Discovery · Problem Framing

Problem Statement Builder

Turn a vague UX or product brief into clearer problem statement options, hidden assumptions, missing information, and next discovery questions.

Choose your AI tool

What tool do you use?

Pick your tool and follow the matching setup. The skill works as a pasteable Markdown prompt, and Claude users can also download a skill package.

Use it in ChatGPT

Download the Markdown skill file.
Open a new ChatGPT conversation.
Paste the full skill file first.
Add your project brief below it.
Ask: "Run this skill on my brief and keep facts separate from assumptions."

Example message

Use the Problem Statement Builder skill below.

[Paste the full Markdown skill file here]

Project brief:
We need to improve onboarding because new users are not activating.
We do not know exactly where they get stuck, but the product team
thinks the setup flow is too long.

Download Markdown

Best when you want a quick, paste-and-run workflow.

Use it in Claude

For one-off use, download the Markdown file and paste it into Claude with your brief.
For reusable use, download the Claude skill package.
Unzip the package and add the skill folder to your Claude-compatible skills location if your setup supports custom skills.
Start a new chat and ask Claude to use "Problem Statement Builder" on your brief.

Example after installing the skill

/problem-statement-builder

Brief:
We need to improve onboarding because new users are not activating.
We do not know exactly where they get stuck, but the product team
thinks the setup flow is too long.

Use the slash-style command if your Claude setup exposes installed skills that way. Otherwise, paste the Markdown skill and brief together.

Download Claude Skill Download Markdown

Use it in Gemini

Download the Markdown skill file.
Open Gemini and paste the full skill instructions.
Add your brief under a clear label such as "Project brief".
Ask Gemini to follow the output format exactly.
Review the assumptions carefully before sharing the output with stakeholders.

Example message

I want you to act as the Problem Statement Builder.
Follow the skill instructions I paste below and use the exact output format.

[Paste the Markdown skill file here]

Project brief:
We need to improve onboarding because new users are not activating.
We do not know exactly where they get stuck, but the product team
thinks the setup flow is too long.

Download Markdown

Best when you want structured discovery output from pasted context.

Use it in Codex

Download the Markdown file into your project or notes folder.
Open a Codex task and reference the file.
Paste or attach your product brief.
Ask Codex to run the skill and produce a discovery-ready artifact.
Use the output to decide the next research or stakeholder conversation.

Example message

Use this file as the skill:
public/resources/ai-skills-for-problem-discovery/downloads/problem-statement-builder.md

Run it on this brief:
We need to improve onboarding because new users are not activating.
We do not know exactly where they get stuck, but the product team
thinks the setup flow is too long.

Download Markdown

Best when the skill belongs alongside project files.

When to use it

Use this skill when a request is broad, solution-shaped, or unclear: improve onboarding, redesign the dashboard, increase conversion, or make the product easier to use.

What you need

Project brief or stakeholder request.
Product or service context.
Known users, business goals, pain points, and evidence.
Constraints, deadlines, and stakeholders involved.

What you get back

A plain-language version of the brief.
Known context separated from assumptions.
Missing information that affects problem framing.
3 to 5 problem statement options.
Discovery questions and one recommended next step.