Product Requirement Analyzer

Problem

Product managers and engineers often jump straight to feature lists without explaining why users need the product, why they choose it over alternatives, or what evidence supports the claim. Public docs and feature comparisons can easily turn correlation into causation or present unverified assumptions as conclusions. Product Requirement Analyzer turns requirement discussions into a traceable, falsifiable reasoning chain.

How it works

The skill organizes analysis around needs first, features second, and validation last:
- Psychological need mapping: uses evolutionary drives, JTBD, and SDT to identify functional, emotional, and social needs.
- Competition and gaps: combines substitution difficulty, KANO, and the importance–satisfaction matrix to find high-importance, low-satisfaction gaps.
- Implementation bridge: uses the Y model and user stories to turn needs into PRD-ready feature descriptions.
- Prioritization and testing: uses RICE or MoSCoW to rank work, then rewrites core conclusions into falsifiable hypotheses.

Simple products can use a lightweight path: identify the dominant drive, write one job story, bucket three requirements, and flag one hypothesis.

Limits

It is useful for early-stage products, competitive analysis, and requirement reviews, but it does not make irreversible product decisions. When information is missing, it asks for clarification rather than guessing. Author-derived mappings are treated as hypotheses, and final validity is confirmed by users, interviews, or evidence.