bmad-check-implementation-readiness

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

Updated Aug 25, 2024
One-click install
npx skills add https://github.com/LeGeRyChEeSe/LanPlay-DiscordBot --skill bmad-check-implementation-readiness-legerycheese
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bmad-check-implementation-readiness
Source: https://github.com/LeGeRyChEeSe/LanPlay-DiscordBot/tree/main/bmad/src/bmm-skills/3-solutioning/bmad-check-implementation-readiness
Command: npx skills add https://github.com/LeGeRyChEeSe/LanPlay-DiscordBot --skill bmad-check-implementation-readiness-legerycheese

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 artifacts to catch gaps, misalignments, and structural 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 Enforcement: Checks epics deliver user value (not technical milestones), verifies no forward dependencies exist, and reviews story sizing and acceptance criteria. - Use Case: A product manager finishing the planning phase runs this assessment to confirm all 42 FRs from the PRD are mapped to stories and receives a readiness report listing 3 critical gaps to fix before sprint one. ## 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 is ready for implementation?▼

Run the implementation readiness workflow, which discovers your PRD, architecture, epics, and UX documents, extracts all functional and non-functional requirements, and validates each requirement is covered by epics and stories before producing a readiness report.

How to validate epic and story coverage against requirements?▼

The workflow extracts every FR from the PRD, reads the epics document for its FR coverage mapping, and builds a coverage matrix showing which requirements are covered and which are missing, with severity-ranked recommendations.

What documents are required for the readiness assessment?▼

The assessment 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 generate warnings that affect the final readiness status.

What happens if duplicate PRD versions exist?▼

The document discovery step flags whole-file and sharded duplicates as critical issues and halts until you confirm which version to use. It will not proceed with unresolved duplicates to avoid assessing conflicting sources.

What epic quality issues does the readiness check detect?▼

It detects technical epics lacking user value, forward dependencies where stories require future work, oversized stories, vague acceptance criteria, and premature database table creation, each documented with severity and remediation guidance.