bmad-check-implementation-readiness

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

Updated May 22, 2026
One-click install
npx skills add https://github.com/Asygnuz-S-A-S/one-star --skill bmad-check-implementation-readiness-asygnuz-s-a-s
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bmad-check-implementation-readiness
Source: https://github.com/Asygnuz-S-A-S/one-star/tree/main/.claude/skills/bmad-check-implementation-readiness
Command: npx skills add https://github.com/Asygnuz-S-A-S/one-star --skill bmad-check-implementation-readiness-asygnuz-s-a-s

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, misalignments, and quality violations 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 confirms which versions to assess. - Requirements Traceability: Extracts all Functional and Non-Functional Requirements from the PRD and validates each one is covered by epics and stories, 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: A product manager finishing the planning phase runs this check to receive a readiness report listing critical gaps—like an uncovered FR or a technical epic with no user value—before handing off to developers. ## Quick Start Ask the assistant 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 PRD, architecture, UX, and epic documents, extracts all functional requirements, and verifies each one is covered by an epic or story. It produces a readiness report with a coverage matrix and recommendations.

What documents are needed for an implementation readiness assessment?▼

The workflow searches for PRD, Architecture, Epics and Stories, and UX documents in your planning artifacts folder, supporting both whole Markdown files and sharded folder structures. Missing documents are flagged as warnings in the final report.

How do I validate that epics cover all functional requirements?▼

The workflow extracts every FR and NFR from the PRD, then compares them against the FR coverage claimed in the epics document. It generates a coverage matrix showing which requirements are covered and lists any missing FRs with impact and remediation guidance.

What epic quality issues does the readiness check detect?▼

It flags technical epics with no user value, forward dependencies where a story requires future work, oversized stories, vague acceptance criteria, and database tables created before they are needed. Violations are categorized as critical, major, or minor.

Can the readiness check handle missing UX documentation?▼

Yes. If no UX document exists, the workflow assesses whether the PRD implies a user interface and adds a warning to the report when UX is implied but undocumented. When UX docs exist, it validates alignment with both the PRD and architecture.