prd

To convert meeting notes into a structured PRD, provide the Markdown file path of your notes to generate a coherent draft. The tool reads your input and produces a business-ready document with explicit gaps and success criteria for stakeholder alignment.

Structuring ambiguous customer requests into business requirements involves applying outside-in framing to identify what the product should do rather than how. This process fills information gaps by asking targeted questions to ensure non-technical stakeholders can agree on the requirements.

Generating a PRD does not strictly require prior project context, but the tool tries to load files like CLAUDE.md and prior PRDs to enrich the draft. If key business information is missing, it asks targeted questions to fill the gaps.

To ensure a product requirements document stays business-focused, apply What>How framing and avoid internal paths. This approach guarantees the output remains an external-facing PRD for stakeholder alignment rather than a detailed technical software requirements specification.

The gap analysis included when creating a PRD identifies missing business information by comparing your raw notes against project context. It highlights explicit gaps and defines measurement and success criteria directly within the generated document draft.