Audit a PRD
Use the prd-spec-verifier MCP server to produce an evidence-based structural audit.
Workflow
- Read the complete PRD without rewriting it.
- Split it into sections and map each section to the closest
section_typeaccepted by thevalidate_prd_documenttool schema. Ask for clarification when a mapping is genuinely ambiguous. - Call
validate_prd_documentwith every mapped section, preserving content exactly. The report is paged: while__page.next_offsetis notnull, call again with the same arguments anditem_offsetset to it, and read the violations of every page. - Report each violation with its rule identifier, severity, affected section, and the evidence returned by the tool.
- Group repeated findings and distinguish blocking violations from warnings.
- State the scope limit: a passing report demonstrates conformance to the implemented structural rules only. It does not establish factual accuracy, product value, implementation feasibility, security, or semantic correctness.
Do not invent a pass for checks the tool did not run. Do not silently repair the PRD unless the user also asks for edits.