TypingMindTypingMindThe best frontend for AI
Define Problem Statement logo

Define Problem Statement

Organization
product-on-purpose
define-problem-statement

Creates a clear problem framing document with user impact, business context, and success criteria. Use when starting a new initiative, realigning a drifted project, or communicating up to leadership.

Overview

Publisherproduct-on-purpose
Repositorypm-skills
Skill namedefine-problem-statement
Stars
717
Forks
92
Bundled files
5
LicenseApache-2.0
Links
Skill sourceRepositoryHomepage
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 5 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by product-on-purpose on GitHub. Read the source before you install it.

Installation

Install the Define Problem Statement AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/product-on-purpose/pm-skills/tree/main/skills/define-problem-statement
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/product-on-purpose/pm-skills.git /tmp/pm-skills
mkdir -p .claude/skills
cp -r /tmp/pm-skills/skills/define-problem-statement .claude/skills/define-problem-statement
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Define Problem Statement in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Define Problem Statement on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Define Problem Statement is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Problem Statement

A problem statement is a concise document that frames the problem you're solving, articulates the impact on users and the business, and defines clear success criteria. It serves as the foundation for all subsequent product work by ensuring alignment on what problem to solve before jumping to how to solve it.

When to Use

  • Starting a new initiative or project to establish shared understanding
  • Realigning a drifted project back to its original intent
  • Communicating up to leadership or stakeholders about priorities
  • Evaluating whether a proposed solution actually addresses the core problem
  • Onboarding new team members to provide context

When NOT to Use

  • The problem is already agreed and engineering needs the spec -> use deliver-prd
  • You want to propose and compare solution approaches -> use develop-solution-brief
  • You are capturing customer motivation rather than a business problem -> use define-jtbd-canvas
  • The "problem" is really an unvalidated assumption -> frame it with define-hypothesis and test it before committing a team to it

Instructions

When asked to create a problem statement, follow these steps:

  1. Identify the User Segment Ask who is experiencing this problem. Get specific about the user persona, role, or segment. Avoid vague descriptions like "users" - instead target "mobile shoppers completing checkout" or "enterprise admins managing 50+ users."

  2. Understand the Pain Points Explore what friction, frustration, or unmet need the user experiences. Ask probing questions to understand the severity and frequency of the problem. Look for evidence from user research, support tickets, or behavioral data.

  3. Establish Business Context Connect the user problem to business impact. How does this problem affect revenue, retention, growth, or strategic goals? Why should the organization invest in solving this now versus later?

  4. Define Success Metrics Identify how you will measure success. What metrics will move if this problem is solved? Establish current baselines and target improvements. Be specific and time-bound.

  5. Surface Constraints and Considerations Note any technical limitations, resource constraints, regulatory requirements, or dependencies that will shape the solution space.

  6. Capture Open Questions Document what you don't know yet. What assumptions need validation? What additional research is needed?

Output Format

Use the template in references/TEMPLATE.md to structure the output. A complete problem statement fills every template section: Problem Summary; User Impact; Business Context; Success Criteria; Constraints & Considerations; and Open Questions.

Quality Checklist

Before finalizing, verify:

  • Problem is specific to a defined user segment (not "all users")
  • Impact is quantified with data or reasonable estimates
  • Success metrics have baselines and targets
  • Problem describes the "what" without prescribing the "how"
  • Business context explains why this matters now
  • Open questions are captured for follow-up

Examples

See references/EXAMPLE.md for a completed example.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Define Problem Statement AI skill do?

Creates a clear problem framing document with user impact, business context, and success criteria. Use when starting a new initiative, realigning a drifted project, or communicating up to leadership.

Why use Define Problem Statement on TypingMind?

Because you install it once and use it with any model. Define Problem Statement is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Define Problem Statement in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/product-on-purpose/pm-skills/tree/main/skills/define-problem-statement. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Define Problem Statement?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Define Problem Statement?

As many as you like. As long as a model supports skills, you can use Define Problem Statement with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Define Problem Statement AI skill free?

Yes. It is published on GitHub by product-on-purpose under the Apache-2.0 license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

Related AI Skills

View all
openclaw logo

Release Openclaw Plugin Testing

openclaw
OrganizationPopular

Plan and run pre-release OpenClaw plugin validation across bundled plugins, package artifacts, lifecycle commands, doctor/fix, config round-trip, gateway startup, SDK compatibility, Docker E2E,…

82.2K
391K
1 files
View
openclaw logo

Solid

openclaw
OrganizationPopular

Write, port, review, or test Solid 2 UI in OpenClaw (Control UI, plugin views, Canvas hosts), including state ownership, Lit interop during the migration, native overlays, testing, performance, and…

82.4K
391.7K
9 files
View
openclaw logo

Auto Qa

openclaw
OrganizationPopular

Run OpenClaw-wide autonomous QA and live/stress campaigns across independent subsystem lanes, with verified fixes and a resumable evidence report.

82.2K
391K
5 files
View
openclaw logo

Autoreview

openclaw
OrganizationPopular

Structured code review when explicitly requested, preferring OpenAI/Codex before Claude.

82.2K
391K
12 files
View

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇