pm-sin-mapper

Describe the symptom and funnel stage in plain language, and the skill runs Debug mode: it maps the symptom to likely sins, inspects qualitative and quantitative evidence, ranks root cause hypotheses, and proposes the smallest safe intervention with before-and-after validation checks.

It is a heuristic that audits a product against seven normalized failure patterns: Blindness, Vanity, Clutter, Misfit, Isolation, Disrespect, and Myopia. Each finding gets a severity rating, supporting evidence, product impact, and a correction, with assumptions labeled explicitly.

Use Brainstorm mode to generate a concept options table showing each idea's core user value, biggest sin risk, and fastest validation test. The skill rejects options with high Blindness or Disrespect and recommends one winner, one runner-up, and one option to avoid.

Use draft-prd when the task is standard requirements writing without a diagnostic lens, or when the sin diagnosis is already complete and you need a formal feature brief or backlog artifact. Sin mapping is for diagnosis and direction comparison, not specification writing.

The framework is a practical heuristic, not a canonical doctrine, and public taxonomies vary. Severity ratings depend on available evidence, so weak or incomplete evidence must be labeled as an assumption rather than treated as fact.