generate-prd

To generate a Product Requirements Document, provide a brief project or module description. The AI uses a strict structure to define the 'what' and 'why' of your product, asking targeted questions to clarify missing details before creating the comprehensive document.

A well-structured PRD must include mandatory sections like Overview, Stakeholders, Scope, and Requirements. Using an automated generation process ensures this predefined structure is followed, keeping the document clear, concise, and focused on product objectives rather than implementation details.

Yes, you can create a PRD with just a brief project description. The generation process identifies missing information and asks targeted questions in Portuguese to gather necessary details about user flows and objectives, ensuring the final requirements document is accurate and complete.

No, the PRD generation process strictly focuses on defining the 'what' and 'why' of a product, not the technical 'how'. It adheres to specific output rules to ensure clarity and conciseness in product specification without delving into technical implementation solutions.

The interactive requirements gathering process asks clarifying questions in Portuguese (pt-BR). This ensures accurate information gathering for users communicating in Portuguese, while maintaining the strict document structure required for comprehensive product specifications.