bmad-check-implementation-readiness

Validate BMAD planning artifacts for completeness, requirements coverage, and UX alignment.

1|Updated Mar 31, 2026
One-click install
npx skills add https://github.com/mol4/BMAD-Board --skill bmad-check-implementation-readiness-mol4
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-check-implementation-readiness
Source: https://github.com/mol4/BMAD-Board/tree/main/BMAD%20board/.agents/skills/bmad-check-implementation-readiness
Command: npx skills add https://github.com/mol4/BMAD-Board --skill bmad-check-implementation-readiness-mol4

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams verify that planning artifacts are complete, consistent, and ready for implementation before development work begins, reducing the risk of missing requirements, weak traceability, and misaligned delivery plans.

Core Features & Use Cases

  • Document discovery and inventory: Finds the relevant PRD, architecture, epics, and UX artifacts and organizes them for review.
  • Requirements extraction and traceability: Pulls functional and non-functional requirements from the PRD and checks whether epics and stories cover them.
  • UX and quality validation: Confirms UX documentation exists when needed, checks alignment with architecture, and flags weak epic or story structure.
  • Use Case: A product manager can run this Skill before Phase 4 implementation to spot missing requirements, uncovered scope, and readiness blockers in a BMAD project.

Quick Start

Use the bmad-check-implementation-readiness skill to assess whether the PRD, UX, architecture, and epics are complete and aligned before implementation begins.

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 check implementation readiness for PRD and epic documents?

Implementation readiness is checked by validating document completeness, requirements coverage, and epic quality across PRD, architecture, and UX artifacts. This Skill inventories planning documents and reports traceable gaps before development begins.

What is requirements traceability and how does it validate epic coverage?

Requirements traceability maps functional and non-functional PRD requirements to epics and stories. This Skill extracts requirements and flags any uncovered scope to ensure delivery plans are fully aligned.

How do I validate UX alignment with architecture before implementation?

UX alignment is validated by confirming UX documentation exists when needed and checking its consistency with architecture documents. This Skill flags misaligned delivery plans and weak story structures.

When do I need to run a BMAD implementation readiness check?

You need a readiness check before Phase 4 implementation in a BMAD project. Product managers run this to spot missing requirements, uncovered scope, and readiness blockers in repositories using PRD and epic documents.

Can I use this implementation readiness check for product management artifacts outside BMAD?

This readiness check applies to pre-implementation reviews in repositories using PRD, architecture, epics, and story documents to coordinate delivery. It requires sequential workflow execution and single-step file loading to validate artifacts.

Why does implementation readiness validation fail on incomplete epic structures?

Readiness validation fails when epics have weak structures or lack coverage for extracted PRD requirements. This Skill reports these gaps as traceable risks, preventing misaligned delivery plans from proceeding to implementation.