bmad-check-implementation-readiness

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

Updated Aug 3, 2026
One-click install
npx skills add https://github.com/shaahy/quicknav-desktop --skill bmad-check-implementation-readiness-shaahy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bmad-check-implementation-readiness
Source: https://github.com/shaahy/quicknav-desktop/tree/main/A%20%E6%95%99%E7%A8%8B%E9%9B%86%E5%90%88/BMAD-METHOD%E6%8A%80%E8%83%BD%E9%80%9F%E6%9F%A5/source-v6.10.0/src/bmm-skills/3-solutioning/bmad-check-implementation-readiness
Command: npx skills add https://github.com/shaahy/quicknav-desktop --skill bmad-check-implementation-readiness-shaahy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Before starting implementation, teams often discover that requirements are missing, epics don't cover all functional requirements, or UX and architecture documents are misaligned. This Skill systematically audits your planning artifacts to catch gaps, duplicates, and quality violations before they become costly development problems. ## 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 Phase 3 solutioning runs this check to confirm all 42 FRs from the PRD are mapped to stories and that no epic depends on future work before developers begin sprint planning. ## Quick Start Ask the assistant 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 is ready for development?▼

Run an implementation readiness check that extracts all functional and non-functional requirements from the PRD, then validates each one is covered by epics and stories. The workflow produces a coverage matrix and a final readiness report with recommendations.

What documents are needed for an implementation readiness assessment?▼

The assessment looks for four document types: PRD, architecture, epics and stories, and UX design documents. It supports both whole Markdown files and sharded folder structures, and flags duplicates or missing documents before analysis.

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

The workflow extracts every FR from the PRD and compares it against the FR coverage claimed in the epics document. Any requirement not mapped to an epic or story is documented as a gap with impact and remediation recommendations.

What makes an epic fail a quality review?▼

Epics fail when they are technical milestones without user value, depend on future epics, contain stories with forward dependencies, or have vague acceptance criteria. Database tables created upfront instead of when needed are also flagged.

Does the readiness check work without a UX document?▼

Yes, but if the PRD implies a user interface and no UX document exists, the assessment records a warning. When UX documentation is present, it validates alignment between UX, PRD, and architecture decisions.