bmad-check-implementation-readiness

To verify implementation readiness, analyze your PRD, Architecture, and Epics for end-to-end traceability, completeness, and UX alignment. This process surfaces gaps, inconsistencies, and unaddressed dependencies before development begins, ensuring safer and faster delivery.

Requirements traceability links PRD specifications directly to epics and stories. You need to validate it during project planning to identify gaps and unaddressed dependencies early, ensuring all planning artifacts are complete and aligned before coding starts.

Finding gaps between UX specifications and epics requires a structured readiness assessment that cross-references planning artifacts. It applies step-by-step checks to identify misalignments, surfacing inconsistencies and providing actionable remediation guidance for unaddressed dependencies.

No, a formal Architecture plan is required alongside your PRD and epics. The readiness validation process checks alignment across all three artifacts, so missing any prevents a complete assessment of dependencies, traceability, and overall implementation readiness.

The best way to enforce a structured readiness process is applying step-by-step checks with documented progress tracking. This certifies that PRD, Architecture, and UX artifacts are complete and aligned, providing clear remediation guidance for any identified gaps.

Your project needs formal readiness validation to catch unaddressed dependencies and inconsistencies between PRD, Architecture, and UX artifacts before implementation. This traceability analysis prevents downstream delivery failures and accelerates development by ensuring complete alignment.