Verified:GitHub

customer-problems

Identify and document Customer Problems from Step 0 business context using Subject-Verb format with penalties and classifications.

1|Updated Mar 31, 2026

Search Tags:#requirements #stakeholders #business-context #customer-problems #problem-based-srs #cp-generation #cp-normalization

Ready to run

npx skills add https://github.com/shirogin/jesuph-skills --skill customer-problems

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: customer-problems
Source: https://github.com/shirogin/jesuph-skills/tree/main/.agents/skills/customer-problems
Command: npx skills add https://github.com/shirogin/jesuph-skills --skill customer-problems

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identify, document, and validate Customer Problems from business context to justify why a solution is needed and guide subsequent artifacts.

Core Features & Use Cases

Discover and normalize customer problems from business context
Classify problems into obligations, expectations, or hopes
Provide ready-to-use CP statements for downstream requirements artifacts
Reference and align with Step 0 business context for consistency

Quick Start

Generate CPs from your Step 0 business context and deliver clearly formatted CP statements.

Frequently Asked Questions about customer-problems

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

FAQPage Schema

How do I identify customer problems from business context to justify software requirements?▼

To identify customer problems from business context, extract stakeholder needs and document them using a structured format. This process translates raw context into clear problem statements to justify why a software solution is needed for downstream requirements.

What is the correct format for writing customer problem statements?▼

The correct format for customer problem statements is [Subject] [Verb] [Object] [Penalty]. This structure captures the specific stakeholder, the action, the target, and the resulting business consequence to ensure clear requirements documentation.

How do I normalize draft customer problems during a requirements review?▼

To normalize draft customer problems, review each statement to ensure it follows the [Subject] [Verb] [Object] [Penalty] format. Normalization adds classifications, consequences, and benefits to align the problems with the step zero business context.

How should I classify customer problems when documenting business context?▼

Classify customer problems into three categories: obligations, expectations, or hopes. This classification clarifies the severity and nature of the stakeholder needs, helping prioritize the software work needed to address each specific problem.

When do I need to generate customer problems for a software project?▼

You need to generate customer problems during the initial step zero business context phase or when reviewing draft requirements. Generating these problems early justifies the software work and provides ready-to-use statements for downstream artifacts.

What should a normalized customer problem statement include beyond the basic format?▼

Beyond the [Subject] [Verb] [Object] [Penalty] format, a normalized customer problem statement should include problem classifications, business consequences, and expected benefits. These elements provide complete context for subsequent requirements artifacts.