product-requirements-review

Conducts structured product requirements review from idea to design doc. As PM asks clarifying questions; analyzes essence (problem, audience, real demand, business logic); researches competitors and data; as CTO assesses technical feasibility and Vibecode cost/time; then proposes creative, shortest-path solutions (smart, non-generic, with unique value or cold-start); makes go/no-go; if go, produces concept, name, architecture, user flows, system design (Vibecode-oriented), design references, and full design document. Principles: no process for its own sake, challenge ideas directly, common sense, evidence-based, output ready for Cursor. Use when the user shares a product idea and wants a professional product review or design document.