bmad-check-implementation-readiness

To check implementation readiness, validate your PRD, UX, architecture, and epics for completeness and alignment. This extracts requirements, verifies FR-to-epic coverage, and enforces story quality to ensure confident implementation.

Requirements traceability maps Functional and Non-Functional Requirements from your PRD directly to epics and stories. Identifying missing coverage prevents wasted engineering time by spotting planning gaps before Phase 4 implementation begins.

Validate UX and architecture alignment by checking that UX documentation exists and aligns with PRD needs and architecture decisions. The readiness check warns you when UX is implied but missing from your planning docs.

Yes, you can use Python scripts to automate epic and story quality gates. The stepwise workflow execution enforces epic user-value quality and checks story independence and dependency correctness using best practices.

Implementation readiness check works without complete UX documentation by actively warning when UX needs are implied but missing. It still reviews available docs to confirm alignment between existing UX needs, PRD, and architecture.

You should not use an implementation readiness check if you have already passed Phase 4 implementation, as it is specifically designed to validate planning completeness and requirement extraction before the build phase starts.