bmad-check-implementation-readiness

To check implementation readiness, validate completeness, alignment, and traceability across PRD, architecture, UX, and epics to catch planning gaps before development starts. You extract requirements, map coverage to epics, and enforce epic quality rules.

Requirements traceability validation extracts functional and non-functional requirements from the PRD and checks whether epics and stories fully cover them. It ensures every documented requirement maps to an actionable implementation item.

Validating epic and story quality involves evaluating whether epics deliver user value, whether stories are independently completable, and whether forward dependencies or weak acceptance criteria block readiness before passing a phase-gate check.

Yes, document discovery and conflict detection finds PRD, architecture, epic, and UX files, groups sharded documents, and flags duplicate whole-versus-sharded versions for resolution before you proceed with implementation.

Verifying UX and architecture alignment requires consistency checks between UX documents and architecture files. This process identifies unresolved document conflicts and structural gaps that could block development readiness.

The best way to audit PRD coverage is to extract functional and non-functional requirements and perform coverage mapping to epics. This generates an implementation readiness assessment report identifying missing FR coverage and structural defects.