bmad-check-implementation-readiness

To validate implementation readiness, you can orchestrate an end-to-end workflow that assesses PRD, UX, Architecture, and Epics for completeness and alignment. This process enforces traceability, detects missing documents or duplicates, and builds a formal readiness report for stakeholder review.

Requirements traceability links functional requirements directly to PRD specifications to detect gaps and validate FR coverage. By applying traceability during readiness checks, you ensure that every functional requirement is accounted for and that missing documents or duplicates are identified before implementation begins.

To check UX and architecture alignment, run a structured validation workflow that compares UX artifacts against architectural specifications. This stepwise process enforces state tracking and append-only reporting to confirm coherence, surface misalignments, and audit overall epic quality.

Yes, you can generate an implementation-readiness report by initiating a check implementation readiness workflow. The process uses append-only reporting across structured steps to consolidate validation results, detect missing documents, and produce a final report for stakeholder review.

The best way to audit epic quality and detect duplicates is to apply an end-to-end readiness validation workflow. This enforces a stepwise process with state tracking to evaluate epic completeness, satisfy requirements for duplicate detection, and validate FR coverage against the PRD.