bmad-check-implementation-readiness

Name: bmad-check-implementation-readiness
Availability: InStock
Author: yukine5377

Validate PRD, UX, Architecture, and Epics for implementation readiness.

Updated Apr 12, 2026

Search Tags:#architecture #validation #epics #prd #ux #readiness

Ready to run

npx skills add https://github.com/Yukine5377/common --skill bmad-check-implementation-readiness-yukine5377

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: bmad-check-implementation-readiness
Source: https://github.com/Yukine5377/common/tree/main/.cursor/skills/bmad-check-implementation-readiness
Command: npx skills add https://github.com/Yukine5377/common --skill bmad-check-implementation-readiness-yukine5377

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validate PRD, UX, Architecture and Epics specs are complete to prevent rework and misalignment before Phase 4 implementation.

Core Features & Use Cases

Stepwise validation across PRD, Epics coverage, UX alignment, and final assessment.
Ensures traceability from FRs to epics and stories, surfacing gaps early.
Detects blocking gaps and enforces independence of epics and strict forward-dependency checks.
Use Case: A product manager triggers readiness when a user asks to "check implementation readiness" to ensure teams align on deliverables.

Quick Start

Initiate the readiness workflow and follow the step prompts to validate PRD, Epics, UX, and architecture.

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 PRD, UX, and Epics readiness before implementation?▼

Implementation readiness validation automates stepwise checks across PRD, Architecture, Epics, and UX to ensure cross-domain alignment and traceability from FRs to stories before coding begins.

What is implementation readiness validation in product development?▼

Implementation readiness validation is a governance process that detects blocking gaps, enforces epic independence, and checks forward dependencies to prevent rework and misalignment before Phase 4.

How do I check traceability from functional requirements to epics and stories?▼

Traceability checks surface gaps early by validating that every functional requirement maps correctly to epics and stories, enforcing strict forward-dependency checks and step-by-step documentation.

When do I need to run an implementation readiness check for my product specs?▼

Run readiness checks when product specs are drafted and cross-domain alignment is needed, ensuring PRD, UX, Architecture, and Epics are complete to prevent misalignment before implementation.

Can I use readiness validation to enforce epic independence and detect blocking gaps?▼

Readiness validation detects blocking gaps and enforces independence of epics with strict forward-dependency checks, ensuring teams align on deliverables before implementation begins.

What are the limitations of automated readiness validation for product development?▼

Automated readiness validation requires complete PRD, Architecture, Epics, and UX specs as input and focuses on governance, meaning it cannot generate missing specs or replace cross-domain team alignment discussions.