write-prd

To generate a product requirements document, provide a detailed feature description to trigger an iterative clarification process that analyzes your codebase and outputs a structured PRD with user stories and testing strategies.

The best way to ensure technical feasibility during feature planning is to vet requirements against your existing system architecture through codebase analysis, ensuring new modules align with current technical constraints.

To structure a PRD with implementation and testing decisions, use a standardized template that guides you through module design, ensuring all critical sections like user stories and technical approaches are clearly outlined.

Yes, you can use automated PRD generation for complex software design workflows; it orchestrates a multi-step planning process from problem definition to final documentation to ensure requirements are well-defined before development.

Iterative clarification is needed for product management documentation to resolve ambiguities early, ensuring the final requirements accurately reflect the problem scope and align with existing system architecture.

A key limitation when drafting requirements against an existing codebase is that the generated module designs depend entirely on the accuracy of the provided codebase analysis, meaning undocumented architecture may lead to misaligned implementation decisions.