Check AI Output for Missing Sections
The PRD looks done — but Non-Goals is gone and Requirements jumped above Goals. Section presence and order, checked in one pass.
Overview
The most dangerous document violation is the missing section nobody notices: a PRD without Non-Goals reads fine and ships scope creep. This setup validates a PRD against its six-section structure and catches both the silently-missing Non-Goals and an order violation (Requirements appearing before Goals). Order matters in documents that get reviewed section by section — reviewers navigate by position, and a reordered document breaks their checklist.
Workflow
-
Validate before the review meeting
A structural pass costs seconds; a review derailed by a missing section costs the meeting.
-
Treat order as part of the contract
Reviewers navigate by position — the order warning is about their checklist, not aesthetics.
-
Repair and re-validate
The repair prompt restores Non-Goals and the correct order; a second pass confirms PASS.
Why This Works
- Missing-section detection targets the violation humans skim past
- Order checking respects how structured documents are actually consumed
- Validation before review keeps meetings about substance, not structure
Best for
- Document workflows with section-by-section review
- Templates whose sections carry governance weight
- Teams that learned about missing Non-Goals the hard way
Not for
- Authoring the PRD structure — that's the Markdown Output Builder's PRD setup
- Evaluating requirement quality — presence first, substance is the reviewer's job
Use cases
- Verifying PRDs carry every section before review
- Catching reordered sections that break review checklists
- Making the absent Non-Goals section loudly visible