problem-clarity
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
- Identify the target user.
- Describe the current pain or limitation.
- Measure frequency and severity.
- Identify existing workarounds.
- Judge whether the pain is strong enough to justify a solution.
Output
More from pratikshadake/claude-product-management-skills
prd-critic
Evaluates PRD quality for clarity, testability, and build-readiness across problem clarity, scope, acceptance criteria, edge cases, and metrics. Use before sharing a PRD with engineering to catch gaps early.
25assumption-mapper
Exposes hidden risks by identifying and ranking assumptions across desirability, feasibility, and viability categories. Use when evaluating new products or features to surface the highest-risk assumption to test first.
23launch-readiness
Audits whether a feature or product is truly ready for launch with a structured checklist and readiness status (Ready/At Risk/Not Ready). Use before any product launch to catch critical gaps.
22experiment-design
Designs fast, reliable validation experiments with hypothesis, method, success metric, and decision rules (Ship/Iterate/Kill). Use when you need to validate an assumption or test a product hypothesis before committing resources.
22value-vs-effort
Prioritizes features using structured scoring across user impact, revenue potential, strategic alignment, confidence, and engineering effort. Use when deciding which feature to build next or comparing competing priorities.
21roadmap-reality-checker
Detects unrealistic planning and hidden delivery risks like overcommitment, missing dependencies, resource mismatches, and undefined metrics. Use when reviewing quarterly roadmaps or sprint plans.
21