product-requirements

To generate a PRD for a new feature specification, engage in an interactive dialogue that gathers detailed requirements and outputs a professional Markdown document. This process systematically evaluates business value, functionality, UX, and technical constraints.

The best way to gather product requirements systematically is through a structured, quality-scored dialogue that evaluates business value and functional completeness. This ensures requirements are clear, testable, and actionable before development begins.

Quality scoring for product requirements works by assessing business value, functional completeness, user experience, and technical constraints using a 100-point system. This iterative refinement guides improvements until the requirement meets a 90+ quality threshold.

You need basic technical knowledge to define clear product requirements, as the process evaluates technical constraints alongside business value and user experience. The interactive dialogue guides you to flesh out technical considerations and acceptance criteria.

Yes, you can use this interactive requirements gathering process to create user stories and acceptance criteria. It helps product managers flesh out these details for new features, resulting in a well-structured product requirements document.

Product requirements documents are output in Markdown format. This ensures the generated PRDs are professional, easily readable, and portable for development teams to use directly in their documentation systems.