bmad-check-implementation-readiness

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

Updated Jul 9, 2026
One-click install
npx skills add https://github.com/unbakedcosmos/thumbnailer --skill bmad-check-implementation-readiness-unbakedcosmos
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bmad-check-implementation-readiness
Source: https://github.com/unbakedcosmos/thumbnailer/tree/main/.claude/skills/bmad-check-implementation-readiness
Command: npx skills add https://github.com/unbakedcosmos/thumbnailer --skill bmad-check-implementation-readiness-unbakedcosmos

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 audits your planning documents to catch those gaps before they become costly implementation failures. ## Core Features & Use Cases - Document Discovery & Inventory: Systematically finds PRD, architecture, epics, and UX documents (whole or sharded), flags duplicates, and confirms which versions to assess. - Requirements Traceability: Extracts every Functional and Non-Functional Requirement from the PRD and validates each one is covered by an epic or story, producing a coverage matrix. - Epic Quality Review: Enforces best practices such as user-value-focused epics, no forward dependencies, proper story sizing, and BDD-style acceptance criteria. - Use Case: After drafting a PRD, architecture spec, and epic breakdown for a new product, run this readiness check to receive a report listing missing FR coverage, UX alignment warnings, and a final READY / NEEDS WORK / NOT READY verdict. ## Quick Start Ask the assistant to check implementation readiness for the planning documents in this project.

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 discovers your PRD, architecture, UX, and epic documents, extracts all functional and non-functional requirements, and validates that every requirement is covered by an epic or story before producing a readiness report.

What does a requirements traceability check cover?▼

It extracts all FRs and NFRs from the PRD, compares them against the FR coverage claimed in the epics document, and builds a coverage matrix showing which requirements are covered and which are missing, with impact and remediation notes.

Does the readiness check work with sharded documents?▼

Yes. The discovery step searches for both whole documents and sharded folder structures with index files. If both formats exist, it flags the duplication and requires you to choose one version before proceeding.

What happens if my project has no UX document?▼

The workflow checks whether UX is implied by the PRD, such as user-facing interfaces or web components. If UX is implied but no document exists, it records a warning in the report rather than silently skipping the check.

What epic quality issues does the review catch?▼

It flags technical epics with no user value, forward dependencies between stories, epics that depend on later epics, oversized stories, vague acceptance criteria, and database tables created before they are needed.