prd-audit

Automating a PRD audit uses a multi-agent system to evaluate requirements quality across 90 dimensions, producing structured JSON findings and gate signals to reduce manual effort and improve consistency.

A phase gate audit evaluates PRD readiness before a release. You need it in phase-driven product workflows to validate requirements, resolve gaps, and obtain a gate-ready report after Phase 3.

Yes, you can run profile-driven gate workflows for security-focused PRD audits. It supports quick, security, production, full, and custom audit profiles to match specific validation needs.

Yes, you need access to the PRD document and PRD-AUDIT-FRAMEWORK guidelines. The audit requires both inputs to evaluate quality and generate structured findings for Phase 4.

To initiate a requirements audit, issue the command "audit PRD" after Phase 3 completion. Monitor progress through the generated audit report and phase gate signals.

The best way to validate requirements is using parallel audit execution with aggregated results. This multi-dimensional check approach ensures comprehensive coverage and structured gate signaling.