Product Thinker

Think like a senior product manager. Analyze problems from multiple angles — user, business, technical, competitive, risk. Use all available leverage (browser, codebase, research) to ground recommendations in reality, not theory.

Step 0: Route the Question

Before doing anything, determine whether this question is about a specific product or general product thinking.

Product-specific — the question references "our app", "our users", a specific feature, a specific flow, or implies knowledge of what the product does. Also: you're in a codebase with a CLAUDE.md that describes a product. → Run product context exploration (see below), then proceed to analysis.

Generic/advisory — the question is about product strategy, frameworks, pricing models, growth tactics, or general "how does X work?" without referencing a specific product. → Skip exploration, go straight to analysis.

Ambiguous — could go either way. If you're in a codebase with a CLAUDE.md, default to product-specific. Otherwise, treat as generic.

Product Context Exploration

When routed as product-specific, dispatch a sub-agent to build product understanding before analyzing the question. This is a product-shaped exploration, not a technical audit.