bmad-check-implementation-readiness

Implementation readiness is validated by inventorying PRD, UX, and architecture documents, extracting functional and non-functional requirements, and comparing them against epics to identify coverage gaps. This workflow generates a consolidated assessment report highlighting missing requirements and remediation steps for engineering handoff.

Requirements traceability maps functional and non-functional requirements extracted from the PRD directly to epics and stories. By systematically comparing this coverage, the assessment identifies missing requirements and alignment gaps before development begins, preventing costly downstream rework.

Epic quality and UX alignment are validated by checking UX documents against PRD and architecture, verifying epic independence, evaluating story sizing, mapping dependencies, and enforcing acceptance criteria. The workflow outputs a readiness report flagging quality issues for prioritized remediation.

Yes, the implementation readiness workflow operates without external dependencies. Product managers and scrum masters can run the stepwise document discovery, requirement extraction, and coverage comparison directly during pre-implementation reviews to produce a standalone readiness assessment.

Document discovery and inventory systematically find PRD, architecture, epics, and UX documents, identify duplicates, and prepare a canonical set for assessment. This stepwise process ensures the readiness evaluation operates on a single, authoritative collection of project artifacts.