PMs, how do you actually review a PRD before it ships?

Writing a PRD is taught. Reviewing one isn't.

Most of us learned to write specs from templates and examples, but I've never seen anyone taught how to red-team one: to hunt for the missing edge case, the metric with no baseline, the acceptance criteria that aren't testable. Those gaps usually surface in eng review, a sprint too late.

So I'm curious how this group does it:

- A checklist / rubric, or mostly vibes?

- Which gap bites you most often, metrics, edge cases, scope creep?

- Has any AI tool actually helped you review, not just generate?

I'm building in this space, Thinkr, launching here tomorrow, so this is partly research. But I genuinely want to hear how you review, rubric or not.