rcode-check-implementation-readiness

To check implementation readiness, review PRDs, architecture, UX, epics, and stories together to confirm alignment before build work begins. This cross-artifact readiness check detects coverage gaps, missing requirements, and unresolved blockers to produce a clear READY or BLOCKED assessment.

Cross-artifact traceability confirms that PRDs, UX designs, architecture, epics, and stories align before implementation begins. It is needed for phase-start reviews to identify stale references, duplicate documents, and missing requirements that would otherwise slow product delivery.

Perform a go or no-go assessment by reviewing planning artifacts for alignment and coverage gaps. The readiness check produces a READY or BLOCKED status with specific remediation guidance, helping product and engineering teams decide whether to proceed with implementation.

Yes, you can detect duplicate or missing documents by reviewing PRD, UX, and architecture artifacts together. The readiness check identifies stale references, duplicate document formats, and missing requirements that would create implementation risks and coverage gaps.

When reviewing epics and stories for readiness, look for coverage gaps, missing requirements, stale references, and unresolved blockers. The readiness check reports these implementation risks alongside specific recommendations to remediate alignment issues before development starts.

Implementation fails when requirements, design, and delivery plans are out of sync because PRDs, UX, architecture, epics, and stories contain coverage gaps and missing traceability. The readiness check identifies these misalignments and reports blockers before build work begins.