vision

A structured product discovery interview transforms a fuzzy product idea into a comprehensive product requirements document. By guiding users through ten mandatory categories, it enforces discovery discipline and captures decisions to produce a draft MASTER_PRD ready for immediate review.

A product discovery interview should cover ten categories to build a complete PRD: problem definition, audience, MVP, user journey, business model, competitive landscape, design language, technical constraints, success metrics, and risks. This structured workflow ensures comprehensive project crystallization.

To conduct a product discovery session involving technical and business experts, enforce mandatory agent engagement across key categories. The workflow requires active participation from a product manager, monetization expert, and tech lead to capture critical business and technical decisions for the MASTER_PRD.

Yes, you can generate a master PRD draft directly from an initial project idea without prior documentation. By initiating a new project discovery session and answering targeted interview questions, the workflow crystallizes fuzzy concepts into a structured MASTER_PRD.md file automatically.

The best way to define an MVP and technical constraints is through a structured discovery workflow. By systematically interviewing stakeholders on user journeys and technical requirements, it enforces discovery discipline and captures precise decisions to outline the MVP and technical boundaries for the MASTER_PRD.

Your product roadmap may fail to capture business models and success metrics effectively due to a lack of discovery discipline. Without a structured 10-category interview process enforcing mandatory expert involvement, critical dimensions like monetization and success metrics are often overlooked during crystallization.