prd

To create a Product Requirements Document, use a structured interview workflow to capture the problem, success criteria, scope, constraints, build plan, and risks, generating a tailored Markdown document for your software feature.

A PRD should include the problem statement, success criteria, scope, constraints, build plan, and risks. Documenting these elements for each feature reduces miscommunication and increases the likelihood of successful feature delivery.

An interview workflow guides you through a series of targeted questions to elicit all necessary details, ensuring comprehensive requirement capture and accurate software documentation tailored to your specific feature.

You need to generate a PRD before development for every non-trivial software feature. This ensures structured documentation of requirements and constraints is established, reducing miscommunication prior to the build phase.

Yes, you can use Markdown for generating and managing Product Requirements Documents. The feature-specific PRD is output in Markdown format after you provide the necessary input during the requirement capture interview.

The best way to document feature scope and constraints is through a structured PRD generation process that guides you through specific questions, ensuring all aspects of the feature are documented clearly before development begins.