bmad-check-implementation-readiness

Validate PRD, UX, architecture, epics, and stories for implementation readiness.

4|Updated Apr 26, 2026
One-click install
npx skills add https://github.com/curdx/curdx-flow --skill bmad-check-implementation-readiness-curdx
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-check-implementation-readiness
Source: https://github.com/curdx/curdx-flow/tree/main/.agents/skills/bmad-check-implementation-readiness
Command: npx skills add https://github.com/curdx/curdx-flow --skill bmad-check-implementation-readiness-curdx

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

It prevents wasted engineering cycles by validating that your PRD, UX, architecture decisions, and epics/stories are complete and aligned before Phase 4 implementation begins.

Core Features & Use Cases

  • Spec completeness & alignment validation: Checks whether requirements and planning artifacts are sufficient and consistent (PRD ↔ epics/stories, plus UX ↔ PRD/architecture).
  • Traceability gap detection: Extracts FRs/NFRs from the PRD and compares them against epic coverage to identify missing requirements.
  • Epic and story implementation readiness review: Enforces epic/user-value quality and story independence, and flags forward dependencies or structural violations.

Quick Start

Use the bmad-check-implementation-readiness skill when you say: "check implementation readiness".

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 before starting development?

Implementation readiness checks validate that your PRD, UX, architecture, and epics are complete and aligned before coding begins. This prevents wasted engineering cycles by identifying spec gaps and traceability issues early.

What is requirements traceability gap detection in PRD validation?

Requirements traceability gap detection extracts functional and non-functional requirements from the PRD and compares them against epic coverage. This identifies missing requirements and ensures every FR and NFR is addressed before implementation.

How do I validate epic and story structure for implementation readiness?

Validating epic and story structure enforces epic independence and flags forward dependencies or structural violations. This ensures stories deliver user value independently and avoids blocking issues during development.

When do I need to check spec alignment between PRD, UX, and architecture?

You need spec alignment checks before Phase 4 implementation begins, when validating that requirements and planning artifacts are sufficient and consistent across PRD, epics, stories, UX, and architecture.

Can I verify UX coverage against my PRD and architecture decisions?

Yes, UX coverage validation checks alignment between UX artifacts and PRD or architecture decisions. This ensures user experience specifications are consistent with documented requirements and technical constraints.