bmad-check-implementation-readiness

Requirements traceability connects functional and non-functional requirements extracted from the PRD to their corresponding epics and stories. It maps each requirement to verify complete epic coverage, identifies missing items, and enforces acceptance criteria quality before development begins.

To check epic coverage before implementation, run a readiness validation workflow that extracts functional and non-functional requirements from your PRD, matches them against existing epics and stories, and generates a consolidated readiness report flagging any missing coverage or poor acceptance criteria.

To validate UX alignment, run an implementation readiness check that verifies UX documentation existence and checks its alignment against PRD and architecture decisions. The workflow flags misaligned UX artifacts and enforces epic and story best practices.

Yes, the readiness validation workflow explicitly handles sharded PRD, architecture, epic, story, and UX artifacts. It forces duplicate resolution and requires user confirmation of discovered documents before proceeding with the requirements extraction and traceability analysis.

An implementation readiness check enforces epic and story best practices by flagging technical milestone epics, forward dependencies, and poor acceptance criteria. It produces a final assessment with critical gaps and actionable recommendations to resolve these violations.