prd-refine

To refine a Product Requirement Document, you systematically analyze it section by section to identify gaps and ambiguities, then iteratively address each issue based on severity through targeted clarifications until a final quality gate is met.

The best way to ensure PRD quality is to apply an automated quality gate that checks if all requirements are clear, complete, and meet defined quality standards before the document moves to the development phase.

Guided PRD refinement works by walking you through the document and prompting for targeted clarification on underspecified sections, ensuring all issues are addressed iteratively based on user input and severity.

Yes, you need an existing PRD file because the refinement workflow analyzes the current document to pinpoint areas needing improvement and guides you through addressing those specific quality issues.

Yes, you can analyze product management documentation to pinpoint areas needing improvement, allowing you to iteratively address identified gaps and ambiguities based on their severity and your input.

If your PRD does not meet the final quality gate threshold, the guided refinement process continues to prompt you for clarifications on underspecified sections until all quality standards are satisfied.