bmad-check-implementation-readiness

Implementation readiness validation extracts Functional and Non-Functional Requirements from the PRD, checks that epics and stories cover them, inventories planning artifacts, and enforces UX alignment to prevent wasted engineering cycles before coding begins.

To check requirements traceability, the workflow extracts Functional Requirements and Non-Functional Requirements from the PRD and validates that epics and stories comprehensively cover them. It rigorously reviews epic quality and enforces user story dependency rules end-to-end.

Yes, you can validate PRD and UX alignment before development by running a phase-gating workflow check. The process verifies UX alignment with the PRD and architecture, flags missing documents, and forces resolution before any implementation analysis continues.

The best way to perform planning completeness validation is to execute document discovery that inventories needed planning artifacts. This approach flags duplicates and missing items across your PRD, UX, and architecture, forcing resolution before analysis continues.

Yes, a PRD is required to check implementation readiness because the validation process extracts Functional Requirements and Non-Functional Requirements from it. The workflow then uses these extracted requirements to validate epic coverage and enforce user story quality rules.

Epic coverage validation fails when extracted Functional and Non-Functional Requirements from the PRD are not fully covered by the defined epics and stories. The workflow enforces epic and user-value quality rules, halting progress until missing coverage is resolved.