describe-problem

Define user problems with constraints and success criteria in a structured document.

5|3|Updated Mar 20, 2026
One-click install
npx skills add https://github.com/leifericf/agentic-sdk --skill describe-problem
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: describe-problem
Source: https://github.com/leifericf/agentic-sdk/tree/main/skills/describe-problem
Command: npx skills add https://github.com/leifericf/agentic-sdk --skill describe-problem

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps to clarify the user's problem, constraints, and success criteria, ensuring a clear understanding of the problem before addressing it.

Core Features & Use Cases

  • Problem Clarification: Helps in defining the real user problem in user and business terms.
  • Constraints and Success Criteria: Assists in identifying constraints and desired outcomes.
  • Iterative Clarification: Facilitates an iterative process to understand the problem fully.
  • Documentation: Writes a detailed problem description document for reference.

Quick Start

Run the describe-problem skill to clarify the user's problem and document it.

Frequently Asked Questions about describe-problem

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

FAQPage Schema
How do I define user requirements before starting product development?

Defining user requirements involves clarifying the real problem in user and business terms, identifying constraints, and establishing success criteria. This skill uses an iterative process to refine problem statements and produces a structured problem description document.

What is the best way to document success criteria and constraints for a new project?

Documenting success criteria and constraints requires an iterative clarification process to fully understand the problem. This skill helps define desired outcomes and writes a detailed problem description document for reference.

Why should I focus on problem definition rather than jumping to a solution?

Focusing on problem definition ensures a clear understanding of the user's problem before addressing it. By clarifying constraints and success criteria first, you prevent building solutions that miss the actual user and business needs.

How do I gather requirements to create a structured problem description document?

Gathering requirements for a problem description document involves iteratively refining the problem statement. This skill facilitates that iterative clarification process to capture user requirements, constraints, and success criteria into a final reference document.

Does iterative problem clarification help with complex user requirements?

Iterative problem clarification helps manage complex user requirements by breaking down the problem into clear definitions. It ensures constraints and success criteria are fully understood and documented before solution development begins.