define-problem-statement
This skill guides you through building a concise problem framing document that establishes shared understanding before solution work begins. It walks through identifying affected users, surfacing pain points, connecting to business impact, and defining measurable success criteria—ensuring your team solves the right problem rather than jumping to how.
define-problem-statement creates a structured problem framing document that aligns teams and leadership on what to solve before pursuing solutions.
AI-generated summary based on this skill's SKILL.md
Decision gist · record as of 2026-07-24
define-problem-statement creates a structured problem framing document that aligns teams and leadership on what to solve before pursuing solutions. This skill guides you through building a concise problem framing document that establishes shared understanding before solution work begins. It walks through identifying affected users, surfacing pain points, connecting to business impact, and defining measurable success criteria—ensuring your team solves the right problem rather than jumping to how.
Use it when
- define-problem-statement emphasizes identifying affected users, surfacing their pain points, and connecting those to business impact.
- define-problem-statement helps you communicate project priorities and rationale by structuring the problem with user impact and metrics.
Verify before relying
Read SKILL.md below before installing (6 files). Open directory: indexed for reading, not audited.
Install
product-on-purpose/pm-skills/define-problem-statement · repository language: JavaScript
Open directory. Skills are indexed for reading, not audited. Review a skill's body before installing it.
Frequently asked questions
AI-generated answers based on this skill's SKILL.md and metadata
How do I write a problem statement for a new project?
define-problem-statement guides you to build a concise framing document that establishes shared understanding before solution work begins. Start by identifying affected users and their pain points, then connect those to business impact. Define measurable success criteria so your team solves the right problem rather than jumping to how. The skill walks through each component systematically.
What should a problem statement include to align teams?
define-problem-statement emphasizes identifying affected users, surfacing their pain points, and connecting those to business impact. Include measurable success criteria so leadership and team members share the same definition of what winning looks like. This shared understanding prevents misalignment and ensures everyone focuses on solving the core problem before debating solutions.
How do I frame a problem for stakeholders?
define-problem-statement helps you communicate project priorities and rationale by structuring the problem with user impact and metrics. Present the affected user segments, their pain points, the business consequences, and your success metrics. This framing makes the problem tangible and justifies why solving it matters—giving stakeholders confidence in your direction.
When should I use a problem statement vs. a PRD?
define-problem-statement is your tool for establishing shared understanding before solution work begins. Use it early to align on what to solve and why. A PRD comes later, detailing how you'll build the solution. Problem statements prevent teams from drifting into the wrong solution; they're the foundation that makes your PRD more focused and effective.
How can define-problem-statement help realign a drifting project?
define-problem-statement lets you step back and reframe the core problem and intent. When projects drift, revisiting the original user pain points, business impact, and success metrics often reveals where the team lost focus. Use this skill to rebuild consensus around what you're actually solving, then course-correct before investing more effort in the wrong direction.
What role do success metrics play in a problem statement?
define-problem-statement teaches you to define measurable success criteria as part of your problem framing. Metrics transform vague goals into concrete targets—showing your team and leadership how you'll know the problem is solved. Without them, teams can't agree on what winning looks like, leading to misalignment and wasted effort.
SKILL.md
Rendered from the published skill. Quoted content, verbatim.
<!-- PM-Skills | https://github.com/product-on-purpose/pm-skills | Apache 2.0 -->
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
(truncated - see the full file via the links below)
File tree — 6 files
skills/define-problem-statement/HISTORY.md
skills/define-problem-statement/SKILL.md
skills/define-problem-statement/evals/output-scenarios/checkout-abandonment.md
skills/define-problem-statement/evals/trigger-fixtures.json
skills/define-problem-statement/references/EXAMPLE.md
skills/define-problem-statement/references/TEMPLATE.md
Let your AI agent find skills like this
Example. Real query, live index.
You found this page by searching. An agent finds it by wishing: SkillFed indexes 56,283 agent skills by what they can do, searchable in plain language.
wish › “Create a clear problem statement to align team and leadership on what to solve”
Give your agent the search over MCP, or paste the wish link into any chat. No install? Search from any chat →
Related skills
Develop Solution Brief generates a focused one-page document that frames your proposed solution, highlights essential features, and surfaces trade-offs for stakeholder alignment. Use it to pitch approach, bridge problem understanding to specification, or compare solution options without implementation details.
deliver-prd guides you through building a complete Product Requirements Document that bridges problem understanding and engineering implementation. It structures your specification across goals, functional requirements, scope boundaries, and technical considerations—ensuring teams have clarity on deliverables and success criteria. Use this when you're ready to hand off a feature, epic, or initiative to engineering.
This skill guides you through creating an Architecture Decision Record that captures the reasoning behind significant technical or architectural choices. It follows Michael Nygard's lightweight format to ensure decisions are documented with their context, rationale, and trade-offs—preserving institutional knowledge for future team members. Use it when selecting technologies, establishing development patterns, or documenting constraints that shape your system.
Capture the "why" behind design choices by documenting decision context, alternatives evaluated, and reasoning that led to your solution. This skill preserves institutional knowledge about design decisions, helping teams onboard to existing choices and revisit past reasoning when needed.
Turn meeting outcomes into focused async updates tailored to your audience's role and channel. This skill translates decisions and actions into what-it-means language for non-attendees, surfaces the primary ask upfront, and detects thread continuations from prior updates. Choose from Slack, Teams, email, Notion, or exec-memo variants.
Capture the outcomes of a focused technical or design investigation in a structured format that prevents knowledge loss and enables confident decision-making. This skill guides you through documenting the original question, methodology, evidence-backed findings, and actionable recommendation so stakeholders can proceed or pivot without re-litigating the exploration.