bmad-check-implementation-readiness

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

Updated Apr 9, 2026
One-click install
npx skills add https://github.com/5onyy/essential-ai-agent-skills --skill bmad-check-implementation-readiness-5onyy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bmad-check-implementation-readiness
Source: https://github.com/5onyy/essential-ai-agent-skills/tree/main/.cursor/skills/bmad-check-implementation-readiness
Command: npx skills add https://github.com/5onyy/essential-ai-agent-skills --skill bmad-check-implementation-readiness-5onyy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Before development begins, teams often discover that requirements are missing, epics don't cover all functional requirements, or stories have broken dependencies. This Skill systematically audits your planning documents to catch gaps and misalignments before they become costly implementation failures. ## Core Features & Use Cases - Document Discovery & Inventory: Searches for PRD, Architecture, Epics, and UX documents (whole or sharded), flags duplicates, and resolves version conflicts. - 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, proper story sizing, and BDD acceptance criteria. - Use Case: A product manager finishes drafting a PRD, architecture spec, and epic breakdown, then runs this readiness check to receive a report listing missing FR coverage, UX alignment warnings, and epic quality violations before handing off to developers. ## Quick Start Ask the agent to check implementation readiness for the current 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 development?▼

Run the implementation readiness workflow, which inventories your PRD, architecture, epics, and UX documents, extracts all functional requirements, and verifies each one is covered by an epic or story. It produces a readiness report with an overall status.

What documents are required for an implementation readiness check?▼

The workflow searches for PRD, Architecture, Epics and Stories, and UX documents in your planning artifacts folder, supporting both whole files and sharded folder formats. Missing documents generate warnings that affect the assessment.

How does requirements traceability validation work?▼

The workflow extracts every Functional Requirement from the PRD, then compares them against the FR coverage claimed in the epics document. It builds a coverage matrix showing which FRs are covered and flags any missing requirements with impact and recommendations.

What epic quality issues does the readiness check detect?▼

It flags technical epics with no user value, forward dependencies where stories require future work, oversized stories, vague acceptance criteria, and premature database table creation. Violations are categorized as critical, major, or minor.

What happens if duplicate PRD or epic documents exist?▼

The document discovery step treats duplicates as critical issues and halts until you resolve them. You must choose which version to use and remove or rename the other before the workflow continues.