bmad-check-implementation-readiness

Validate PRD, UX, Architecture, and Epics alignment before Phase 4 implementation.

Updated Sep 27, 2025
One-click install
npx skills add https://github.com/Cbanzaime23/Booking-System --skill bmad-check-implementation-readiness-cbanzaime23
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-check-implementation-readiness
Source: https://github.com/Cbanzaime23/Booking-System/tree/main/.agent/skills/bmad-check-implementation-readiness
Command: npx skills add https://github.com/Cbanzaime23/Booking-System --skill bmad-check-implementation-readiness-cbanzaime23

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validate readiness by verifying PRD, UX, Architecture, Epics, and Stories are complete and aligned before Phase 4 implementation, reducing gaps and miscommunication that can derail delivery.

Core Features & Use Cases

  • Requirements traceability validation: cross-check PRD FRs with epics and stories to ensure full coverage.
  • UX and Architecture alignment checks: confirm UX needs are reflected in architecture decisions and feasible within the design.
  • Gap discovery and risk reporting: surface missing items, ambiguous requirements, and forward dependencies with actionable remediation.

Quick Start

Provide a ready-to-activate readiness assessment for the current PRD, UX, Architecture, and Epics and output a prioritized remediation plan.

Frequently Asked Questions about bmad-check-implementation-readiness

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I validate requirements traceability between PRD and epics before implementation?

You can validate implementation readiness by cross-checking PRD, UX, Architecture, and Epics for completeness and alignment. This process guarantees traceability, maps epics to functional requirements, and outputs a prioritized remediation plan to fix gaps before Phase 4.

What is implementation readiness validation in project planning?

Implementation readiness validation is the process of verifying that PRD, UX, Architecture, and Epics are complete and aligned. It reduces gaps and miscommunication that can derail delivery by ensuring actionable remediation and traceability across planning artifacts.

How do I check UX and Architecture alignment for project planning?

To check UX and Architecture alignment, confirm that UX needs are reflected in architecture decisions and are feasible within the design. This alignment check prevents forward dependencies and ensures design constraints are respected during implementation.

How do I identify requirements gaps and forward dependencies before development?

Gap discovery and risk reporting surfaces missing items, ambiguous requirements, and forward dependencies across PRD and epics. It enforces best practices in requirements management by generating a prioritized, actionable remediation plan to resolve issues.

Can I use architecture validation for PRD and epic traceability without external dependencies?

Yes, you can perform architecture validation and PRD-epic traceability checks without external dependencies. The readiness assessment operates independently on your PRD, UX, Architecture, and Epics data to output a complete prioritized remediation plan.

When should I not use implementation readiness validation for requirements analysis?

You should avoid implementation readiness validation if your PRD, UX, Architecture, or Epics are not yet drafted. The validation requires these planning artifacts to exist so it can cross-check traceability and identify actionable gaps before Phase 4.