Skip to content
Skills Library
Management & product · Planning

problem-definition

/problem-definition

Help users define problems clearly before jumping to solutions. Use when someone is scoping a new feature, validating a product idea, struggling to articulate what they're building, or falling into the "shiny object trap" with new technology.

Licence
CC-BY-4.0
Last repository change
05.11.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
2
Scripts
0
HTML comments
0
URLs in SKILL.md
2
Deprecation

No signals detected. Repository changed on 05.11.2026, without references to retired models or APIs.

Licence

CC-BY-4.0, otwarta.

What it does and when to use it

Help users define problems clearly before jumping to solutions. Use when someone is scoping a new feature, validating a product idea, struggling to articulate what they're building, or falling into the "shiny object trap" with new technology.

Triggers from the description

re building, or falling into the
Original author description

Help users define problems clearly before jumping to solutions. Use when someone is scoping a new feature, validating a product idea, struggling to articulate what they're building, or falling into the "shiny object trap" with new technology.

How it works

  1. Closing
Original SKILL.md headings · 28 lines, 338 words
SKILL.md preview
---
name: problem-definition
description: Help users define problems clearly before jumping to solutions. Use when someone is scoping a new feature, validating a product idea, struggling to articulate what they're building, or falling into the "shiny object trap" with new technology.
license: CC-BY-4.0 AND MIT
metadata:
  author: Alexandros Andre Chaaraoui
  source: https://github.com/alexandrosandre/agentic-engineering
  adapted_from: https://github.com/RefoundAI/lenny-skills
  upstream_license: MIT
---

# Problem Definition

Adapted from the problem-definition skill in RefoundAI/lenny-skills (MIT, Copyright (c) 2025 Refound AI); changes by Alexandros Andre Chaaraoui.

Help the user state the problem before anyone picks a solution: a problem stated as a feature locks in one answer before the need behind it is understood.

1. **Understand the current framing.** Ask how they think about the problem today, and separate the outcome they want from any method they already have in mind.
2. **Find the struggling moment.** The specific situation where a user gets stuck, what they were trying to do right before it, and what they do today to work around it.
3. **Separate the problem from the solution.** A requested feature, or a technology looking for a use, is a candidate answer, not the problem.
4. **Check that the problem matters.** Who has it, how often, and whether it is a customer problem, a business problem, or both. Where it turns on how our users really behave, read their sessions first (the `read-user-sessions` skill) instead of reasoning from assumed behavior.

When the framing stays abstract, make it concrete: a specific person in a specific moment, or a throwaway prototype they can react to (the `prototype` skill).

Questions that usually move it forward:

- "What is the user doing right before they hit this? What are they trying to get done?"
- "Why hasn't this been solved already? What makes it hard?"
- "If this were solved perfectly, what would be different for the user?"
- "What do people do today to work around it?"

Flag these when you see them: starting from a feature or a technology and working back to a problem; a problem stated so broadly it points to no solution; solving an internal metric without a user need behind it.

## Closing

- End your response with a blockquote line: **Skills used:** then each skill name in backticks (this skill: `problem-definition`; include other skills if used).
- If this skill's instructions failed or needed a workaround, update this file.
Files in this package (2)
  • README.md 1 KB
  • SKILL.md 2 KB

Versions

RepositoryScoreLicence
This page · alexandrosandre/agentic-engineering90CC-BY-4.0
viktorbezdek/skillstack100MIT

Database snapshot: 13.11.2026 · package version ea03e3d36987 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100managing-product
    Extracts product requirements and produces a PRD. Use when a user wants to build software and needs to define what to build before architecture or implementation, when scoping an MVP, or when translating a vague idea into a buildable specification.
  • 90plan-definition
    Turn a spark (an idea, even a one-liner, in any format) into a clear product definition through a guided, Socratic discovery phase — frame the problem (users, outcome, metrics, constraints, non-goals), explore 2–4 directions with trade-offs, and produce an approved definition…
  • 100shape
    Guides users from a rough project, product, or feature idea to a concise Product Charter by clarifying the audience, problem, solution, boundaries, and success measure. Use when shaping or scoping a new idea.
  • 85pm-problem-statement
    Write or critique a product problem statement — turning a vague prompt, signal, or feature request into a clear, evidence-grounded, testable statement of the real problem before any solution. Separates the problem from solutions, symptoms, goals, and constraints; applies the…
  • 100om-product-manager
    Use when defining business requirements for a new app or feature — BEFORE any spec or code exists. Triggers on "what should we build", "define requirements", "create app spec", or when user stories lack success criteria. Also use when reviewing existing specs for gaps.
  • 100write-spec
    Write a feature spec or PRD from a problem statement or feature idea. Use when creating product requirements documents.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.