bmad-check-implementation-readiness

To validate PRD, UX, and architecture alignment, run a readiness assessment workflow that verifies documentation completeness, checks traceability to requirements, and detects gaps across epics to prevent rework before coding begins.

Requirements traceability in pre-implementation reviews is the process of verifying that every epic and architecture decision directly maps to PRD and UX requirements, ensuring no missing features and aligning project readiness criteria before development starts.

You need to run an implementation readiness check during release planning or PRD sign-offs to ensure epics, UX, and architecture documentation satisfy readiness criteria and are fully aligned before committing development resources.

Yes, you can use this readiness validation for architecture planning because it performs alignment verification across architecture and epics, actively reporting missing requirements and gaps to inform your decision-making process.

The best way to ensure PRD sign-off readiness is executing a guided readiness assessment workflow that verifies documentation completeness, checks epics alignment, and confirms all readiness criteria are satisfied to prevent future rework.

Project readiness validation works by actively detecting missing requirements and reporting gaps, meaning it can identify incomplete UX and architecture documentation but will flag those gaps as failing readiness criteria before implementation proceeds.