write-a-prd

To write a product requirements document from a vague idea, the system conducts user interviews to resolve ambiguity and explores your codebase to validate assumptions. It then outputs a complete PRD with user stories, module design, and testing decisions.

Codebase exploration improves feature planning by verifying technical assumptions and surfacing affected modules during PRD generation. It identifies existing patterns and constraints to ensure the module design aligns with your current software architecture.

Yes, you can define module-level implementation approaches within the generated PRD. The system designs major modules as deep, testable building blocks, capturing explicit implementation decisions alongside user stories and out-of-scope boundaries.

The best way to align stakeholders on new feature requirements is through structured user interview-driven discovery. This process turns free-form problem descriptions into an unambiguous shared understanding by asking relentless, branch-by-branch questions.

Yes, the PRD generation process explicitly handles edge cases and out-of-scope boundaries. The final document includes exhaustive user stories, explicit testing decisions, and a dedicated section for open questions to clarify project limits.

To start generating a PRD for your software project, you need to provide a detailed feature idea and specify your desired file format and location. The system will then explore the repository, interview you, and save the PRD.