pm-spec-quality-audit

Run a structured audit that checks eight dimensions: problem anchoring, requirement layering, testability, complete flows, scope exclusions, dependencies/constraints/assumptions, validation evidence, and audience fit. Rate each finding by build damage and provide concrete rewrites.

A requirement is testable when QA could write a pass/fail check from it without asking the author for clarification. Replace subjective adjectives like fast or intuitive with a number, unit, and condition, such as loading in under three seconds on a standard mobile network.

A PRD states business and user requirements, a functional spec describes how the product behaves, and a technical spec covers how code achieves it. Audit each document against its own layer's job rather than flagging a PRD for lacking spec-level precision.

Run it when reviewing any spec, PRD, or requirements document, and as the validation step after generating one. It is most valuable before development starts, since post-approval changes cost more.

The most commonly missing sections are scope exclusions and the dependencies, constraints, and assumptions section. Specs also frequently omit error and corner-case flows, leaving only happy-path behavior defined.