bmad-check-implementation-readiness

Validate PRD, UX, Architecture, and epic completeness with a readiness report.

Updated Mar 24, 2026
One-click install
npx skills add https://github.com/imonmi/INTER-EDU --skill bmad-check-implementation-readiness-imonmi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-check-implementation-readiness
Source: https://github.com/imonmi/INTER-EDU/tree/main/_bmad/bmm/workflows/3-solutioning/bmad-check-implementation-readiness
Command: npx skills add https://github.com/imonmi/INTER-EDU --skill bmad-check-implementation-readiness-imonmi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validate that PRD, Architecture and Epics/Stories specs are complete and aligned before Phase 4 implementation starts, ensuring all planning gaps are identified early and actionable.

Core Features & Use Cases

  • Automated workflow-guided validation: PRD completeness, architecture alignment checks, and epic coverage verification across the project artifacts.
  • Traceability and gap detection: identify missing requirements, conflicting documents, and unresolved dependencies to prevent scope creep.
  • Stakeholder collaboration: generate a unified readiness report to drive decisions on proceeding to implementation.

Quick Start

Initiate the Implementation Readiness workflow to begin validating PRD, UX, Architecture, and Epics against the project goals.

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 validate PRD, Architecture, and Epic alignment before implementation kickoff?

To validate alignment before kickoff, run a step-by-step readiness workflow that checks PRD completeness, architecture alignment, and epic coverage across project artifacts to identify planning gaps and ensure traceability.

What is implementation readiness validation and why do I need it?

Implementation readiness validation is the process of consolidating product planning artifacts to ensure PRD, UX, Architecture, epics, and stories are complete. You need it to identify missing requirements and unresolved dependencies early, preventing scope creep.

How do I check traceability and identify gaps between UX designs and Epics?

Check traceability and identify gaps by executing a guided workflow that performs document discovery, UX alignment checks, and epic quality reviews, automatically detecting conflicting documents and missing requirements across your planning artifacts.

Can I generate a stakeholder sign-off report after reviewing PRD and Epic coverage?

Yes, you can generate a unified readiness report for stakeholder sign-off. The workflow consolidates findings from PRD analysis, architecture alignment, and epic quality reviews to drive decisions on proceeding to Phase 4 implementation.

What is the best way to prevent scope creep when consolidating product planning artifacts?

The best way to prevent scope creep is to enforce traceability across PRD, UX, and Architecture documents. This workflow identifies conflicting documents and unresolved dependencies, generating a readiness report to ensure actionable alignment.

Do I need existing PRD and Architecture documents to start the readiness workflow?

Yes, you need existing PRD, UX, and Architecture documents. The workflow begins with document discovery and analyzes these artifacts to verify epic coverage, enforce traceability, and assess overall readiness before implementation starts.