bmad-check-implementation-readiness

Validates PRD, UX, architecture, and epic documents for completeness before implementation.

2|Updated Apr 19, 2026
One-click install
npx skills add https://github.com/Wizarck/nexandro --skill bmad-check-implementation-readiness-wizarck
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bmad-check-implementation-readiness
Source: https://github.com/Wizarck/nexandro/tree/main/skills/bmad-check-implementation-readiness
Command: npx skills add https://github.com/Wizarck/nexandro --skill bmad-check-implementation-readiness-wizarck

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Before development starts, teams often discover that requirements are missing from epics, UX is misaligned with architecture, or stories have broken dependencies. This Skill runs a structured six-step audit of your planning artifacts to catch those gaps before they become costly implementation failures. ## Core Features & Use Cases - Document Discovery: Inventories PRD, architecture, epics, and UX documents, flagging duplicates and missing files. - Requirements Traceability: Extracts all functional and non-functional requirements from the PRD and validates epic coverage with a coverage matrix. - Epic Quality Review: Enforces best practices such as user-value-focused epics, no forward dependencies, and testable acceptance criteria. - Use Case: A product manager finishing the planning phase asks the agent to check implementation readiness, and receives a readiness report listing missing FRs, misaligned UX, and epic quality violations with remediation recommendations. ## Quick Start Ask the agent to check implementation readiness for the project planning documents.

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 if my PRD and epics are ready for implementation?▼

Run the implementation readiness workflow, which inventories your planning documents, extracts all functional and non-functional requirements from the PRD, and validates that every requirement is covered by an epic or story before producing a readiness report.

How to validate requirements traceability between PRD and epics?▼

The workflow extracts all FRs and NFRs from the PRD, then compares them against the FR coverage claimed in the epics document. It produces a coverage matrix showing which requirements are covered and which are missing.

What documents are required for the readiness assessment?▼

The workflow searches for PRD, architecture, epics and stories, and UX design documents in the planning artifacts folder, supporting both whole files and sharded folder formats. Missing documents are flagged as warnings in the report.

What happens if duplicate PRD or epic documents exist?▼

The document discovery step flags duplicates, such as a whole file and a sharded folder version, as critical issues. The workflow halts and requires you to choose one version before proceeding with the assessment.

What epic quality issues does the readiness check detect?▼

The review flags technical epics without user value, forward dependencies between stories, oversized stories, vague acceptance criteria, and database tables created before they are needed. Each violation is documented with severity and remediation guidance.

What is the output of the implementation readiness workflow?▼

The workflow produces a markdown readiness report in the planning artifacts folder containing the document inventory, requirement extraction, coverage matrix, UX alignment findings, epic quality violations, and a final readiness status with recommendations.