trw-audit

To verify code compliance against PRD acceptance criteria, invoke /trw-audit in your project workspace to extract functional and non-functional requirements, map them to implemented code and tests, and generate structured audit findings.

An adversarial PRD audit is an independent verification process that checks code implementations against PRD acceptance criteria to prevent confirmation bias by identifying hidden requirement gaps beyond typical test success.

You can trace non-functional requirements to source and test files by performing keyword-based tracing across the repository, flagging missing test coverage or misalignments between the NFRs and the implemented code.

Yes, this code review approach checks for missing NFR coverage by applying mandatory NFR checklists and performing structured test-quality assessments to ensure non-functional requirements are fully traced.

You generate an auditable report for spec compliance findings by running the audit workflow, which creates a traceable report stored under the scratch/audits directory within your project workspace.

You need an independent audit instead of standard test validation when you want to prevent confirmation bias and detect hidden requirements slipping through by verifying alignment with PRD acceptance criteria beyond typical test success.