Validate PRDs before they reach coder_bot.
A PRD passes only when user intent, MVP scope, input/output rules, SEO elements, and acceptance criteria are explicit.
◎ Ready for handoff
Overall PRD completeness and clarity score.
85Good, but needs fixes
△ 3 missing requirements preventing automated handoff.
▣Pass
PM Clarity
Good enough.
▣Pass
MVP Boundary
Good enough.
▣Fail
SEO Readiness
Metadata missing.
▣Warn
Dev Acceptance
Good enough.
Requirement Checklist
| Requirement | Status | Why it matters | Action |
|---|---|---|---|
| Target user | ● Pass | Defined for clear majority | - |
| MVP feature | ● Pass | Prevents scope creep | - |
| Output spec | ● Fail | UI rendering logic needed | Define states |
| Error states | ● Warn | Handle edge cases gracefully | Add states |
| SEO metadata | ● Fail | Required for marketing site | Fix SEO |
▣ Reject overbuilt PRDs
Clearly list features that fall outside MVP scope.
⊘ Complex accounts⊘ User community⊘ Multi-role permissions⊘ Admin dashboard⊘ Advanced history⊘ Heavy workflows