pm-design-criticlisted

# PM design critic Runs a behavioral and UX review on the surface of a product — the moments a user actually touches. Most PM reviews stop at "is this the right problem and the right strategy." This skill picks up at the layer below: given the strategy is right, is the design choosing the right defaults, putting friction in the right places, framing the right tradeoffs, and ending the right way? Adjacent to `pm-red-team` but narrower. Red-team challenges the strategy. This skill challenges the surface. Both can be run on the same artifact; they'll surface different holes. ## When to use Use this when: - A PRD or design spec is drafted and the user wants a design-layer pass before circulation - A new feature is heading to launch and the user wants one last review of the UX surface - The feature involves an AI-driven interaction and the user wants the AI surface specifically critiqued - The user has a draft that "doesn't feel right" but can't name why — the issue is often a design-principle violation, not a strategy gap Don't use this when: - The problem isn't framed yet — run `pm-decision-coach` or `decision-making/problem-framing.md` first; design critique on a wrong problem is wasted - The user wants strategy-level adversarial pressure — use `pm-red-team` instead - The user wants the five-criterion rubric scored — use `pm-evaluator` - The product is API/backend-only with no user-facing surface — this skill has nothing to grab ## How to apply ### 1. Map the moments fir