bmad-check-implementation-readiness

To check PRD, UX, and Architecture alignment, validate that all cross-functional artifacts are complete and traceable. This readiness check identifies gaps and dependencies across disciplines to ensure alignment before committing to a release cycle.

An epics readiness check looks for gaps, dependencies, and missing traceability across PRD, UX, Architecture, and Stories. It validates that all cross-functional specifications are complete and aligned to prevent gaps before starting Phase 4 implementation.

You need to run a readiness check for PRD and UX specifications right before committing to a release cycle. It ensures all cross-functional artifacts are fully complete, aligned, and ready prior to starting Phase 4 implementation.

Identify gaps and dependencies across epics and architecture specifications by running a full readiness check. This validates traceability and completeness across requirements, architecture, and user experience to guide planning and prevent build-phase gaps.

Yes, you can validate cross-functional artifact readiness for a product team release cycle. The check confirms that PRD, UX, Architecture, Epics, and Stories are complete and aligned, ensuring all disciplines are ready before execution.

Implementation readiness requires traceability across requirements and user experience to prevent gaps before starting Phase 4 implementation. It ensures that PRD, UX, Architecture, and Epics specifications are complete, aligned, and dependent-free.