Critique Product

Preparation

Before anything else, invoke /product-thinking to load strategic context, user segments, and current product landscape.

Then read ALL context files:

• .acumen.md — product strategy and positioning
• .acumen/competitors.md — competitive landscape
• .acumen/personas.md — user segments and behaviors
• .acumen/features.md — current feature catalog
• ./DESIGN.md — visual identity contract (only when critiquing UI-touching artifacts; if missing, flag it)

A critique without context is just opinion. You need to know what the product is, who it serves, and what it's competing against before you can evaluate whether an artifact is good.

Mindset

Read this as if you're the engineer who has to build it, the exec who has to fund it, and the designer who has to make it real. Does it survive all three?