← ClaudeAtlas

problem-clarity-checklisted

Evaluates whether a problem statement is genuinely well-defined before solutioning begins, catching cases where a PRD or spec would be built on a premise that's actually a disguised solution, an unvalidated assumption, or a vague target user. Proactively use this before writing a PRD, spec, or feature doc for any problem statement, user pain point, feature request, or "we should build X" idea that hasn't already been through this check — even if the user doesn't ask for it by name. Do NOT use for casual code requests, bug fixes, or small technical asks with no PRD/spec involved; those should proceed unblocked. Can also be invoked explicitly, e.g. "run a problem clarity check," "sanity check this problem statement," "is this problem well-defined," or "stress-test this premise."
pruthivim/claude-pm-skills · ★ 1 · Web & Frontend · score 64
Install: claude install-skill pruthivim/claude-pm-skills
# Problem Clarity Check A premise-and-definition guardrail. Before a problem statement becomes a PRD, spec, or line of code, this skill tests whether it's a genuine, validated user pain point — or a solution wearing a problem statement's clothes. ## When to run this Run proactively, before starting to write a PRD, spec, or feature doc, whenever the underlying problem hasn't already been validated in this conversation. Do not run it for casual code requests, bug fixes, or small technical tasks — those proceed normally. Also do not run it for documents that explain or justify a decision that's already been made (e.g. "write a doc explaining why we're deprecating X in favor of Y," where the deprecation is stated as settled, not proposed). This skill checks premises *before* a decision is locked in — it's not a retroactive audit of decisions already made, and re-litigating settled decisions when someone just wants an explainer written isn't helpful. If it's ambiguous whether a decision is settled or still being proposed, ask. If the user explicitly asks for a clarity check, diagnostic, or premise stress-test, run it regardless of context. If a problem has already passed this check earlier in the conversation, don't re-run it from scratch for follow-up requests on the same problem — only re-check if the problem statement materially changes. **Scope check before running the criteria**: this skill is built for problems framed around user pain points. Before applying the six c