bmad-check-implementation-readiness

Implementation readiness is checked by validating that planning artifacts like PRDs, epics, and UX files are complete and consistent. You inventory documents, extract requirements, and verify coverage to ensure all functional and non-functional needs are met before development begins.

Requirements traceability is the process of mapping functional and non-functional requirements extracted from a PRD directly to epics and stories. It ensures every documented requirement is covered by planned work and helps identify gaps in product discovery and delivery workflows.

Epic coverage is validated by extracting requirements from the PRD and checking whether the planned epics and stories address each one. This coverage validation flags missing work and ensures no functional or non-functional requirements are overlooked before implementation.

Yes, UX alignment and story independence can be checked across both whole and sharded planning artifacts. The review evaluates UX consistency against best-practice standards and verifies that individual stories remain independent within the broader epic structure during readiness assessments.

A readiness report is needed when transitioning from product discovery to delivery on a SaaS project. Running this multi-step assessment before development begins helps identify gaps in architecture, UX, and story plans, confirming whether the team is actually ready to build.

Automated epic quality review limitations include its reliance on the completeness of existing PRD, architecture, and UX files. It cannot invent missing requirements or fix poor story independence; it only flags these issues based on the internal consistency of the provided planning artifacts.