# Problem clarity engine Human Guide

## What This Is For
Evaluates whether a proposed idea addresses a genuine user problem worth solving. It gives the agent a clearer input/output frame for problem clarity engine: what context to ask for, what decisions to make, and what usable artifact to return.

Use this as a human-readable version of the Problem clarity engine agent skill. It is meant for marketers, operators, founders, and other non-coders who want the workflow without reading agent-specific implementation instructions.

## When To Use This
- Use this when you need a repeatable process for problem clarity engine.
- Use this when the task needs judgment, examples, constraints, or a clear output format rather than a one-off prompt.
- Use this when you want to hand an AI assistant enough context to produce a usable marketing artifact.

## When Not To Use This
- Do not use this when you only need a quick factual answer.
- Do not use this when the work depends on private data you cannot share with the assistant.
- Do not use this as a replacement for legal, compliance, financial, or medical review.

## What You Need Before Starting
- The goal or business outcome you want.
- The audience, customer segment, or market context.
- Any source material the assistant should respect, such as notes, briefs, examples, URLs, or brand guidance.
- Constraints such as tone, length, channel, deadline, region, or approval requirements.
- A clear definition of what a good final answer should look like.

## Step-By-Step Workflow
1. State the job clearly: "Use the Problem clarity engine guide to help me with..."
2. Add context: audience, goal, offer, channel, source material, and constraints.
3. Ask the assistant to identify missing inputs before producing the final output.
4. Have the assistant follow the skill-specific guidance below.
5. Review the result against the final checklist and ask for revisions where needed.

## Skill-Specific Guidance
- Describe the current pain or limitation.
- Measure frequency and severity.
- Identify existing workarounds.
- Judge whether the pain is strong enough to justify a solution.
- Notes scattered across tools
- Frequent follow-up confusion
- Manual note-taking during calls
- Recording meetings but never revisiting

## Decision Points And Nuance
The original skill emphasizes: Purpose, When to Use, Steps, Output, Target User, Core Problem, Evidence of Pain, Current Workarounds, Severity Assessment, Verdict.

Use these questions to steer the work:
- What is the intended audience or buyer?
- What source material must be preserved?
- What should the assistant optimize for: clarity, persuasion, accuracy, speed, creativity, or conversion?
- What examples represent the desired quality bar?
- What should the assistant avoid?

## Common Mistakes
- Recording meetings but never revisiting

## Copy-And-Paste Prompt
```text
Use the Problem clarity engine human guide.

My goal:
[Describe the business outcome]

Audience:
[Describe who this is for]

Context and source material:
[Paste notes, examples, links, or existing copy]

Constraints:
[Tone, length, channel, timeline, must-include items, must-avoid items]

Before producing the final output, ask me for any missing information that would materially improve the result.
```

## Final Checklist
- [ ] The output matches the original goal.
- [ ] The audience and context are reflected in the answer.
- [ ] Important constraints and source material were preserved.
- [ ] The assistant made the relevant decisions explicit.
- [ ] The final artifact is ready to use, review, or hand to the next person.

## Source
This guide was generated from the pratikshadake/claude-product-management-skills skill entry for `problem-clarity`.

## Source Skill Notes
These notes preserve the nuance from the original skill. Use them as supporting reference when the workflow above feels too generic.

# Problem Clarity Engine

## Purpose
Determine whether a proposed idea represents a real, meaningful user problem
worth solving.

## When to Use
- New feature ideas
- Startup concepts
- Vague user complaints

## Steps
1. Identify the target user.
2. Describe the current pain or limitation.
3. Measure frequency and severity.
4. Identify existing workarounds.
5. Judge whether the pain is strong enough to justify a solution.

## Output

### Target User
### Core Problem
### Evidence of Pain
### Current Workarounds
### Severity Assessment
High / Medium / Low

### Verdict
Worth Solving / Not Worth Solving

## References
See [worked example](references/example.md) for a complete scenario.

---

## Supporting file: references/example.md

# Example: Problem Clarity — AI Meeting Notes

## Target User
Startup founders who attend many Zoom meetings.

## Core Problem
They forget key decisions and action items after meetings.

## Evidence of Pain
- Notes scattered across tools  
- Frequent follow-up confusion  
- Manual note-taking during calls  

## Current Workarounds
- Writing notes manually  
- Recording meetings but never revisiting  

## Severity Assessment
High

## Verdict
**Worth Solving**