bmad-check-implementation-readiness

Validate PRD requirements traceability and generate an implementation-readiness report.

Updated Apr 2, 2026
One-click install
npx skills add https://github.com/amitmishra-byldd/Bmad-Note-Maker --skill bmad-check-implementation-readiness-amitmishra-byldd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-check-implementation-readiness
Source: https://github.com/amitmishra-byldd/Bmad-Note-Maker/tree/main/_bmad/bmm/3-solutioning/bmad-check-implementation-readiness
Command: npx skills add https://github.com/amitmishra-byldd/Bmad-Note-Maker --skill bmad-check-implementation-readiness-amitmishra-byldd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill validates that PRD, architecture, epics, stories, and UX artifacts are complete, aligned, and ready for Phase 4 implementation, reducing the risk of missed requirements and planning gaps.

Core Features & Use Cases

  • Document Discovery: Systematically inventory PRD, Architecture, Epics, and UX artifacts and identify duplicates or missing files.
  • Requirements Traceability: Extract and map Functional and Non-Functional Requirements from PRD to epics and stories to reveal coverage gaps.
  • Quality & Alignment Checks: Assess epic/story quality, forward dependencies, UX alignment, and architectural support, then generate a consolidated readiness report.
  • Use Case: Run this before a development kickoff to ensure every PRD requirement has a traceable implementation path and to surface critical gaps that block implementation.

Quick Start

Run the implementation readiness workflow to inventory planning artifacts, validate PRD-to-epic coverage, check UX and architecture alignment, and produce the readiness report.

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 implementation readiness before development kickoff?

Implementation readiness checks validate that PRD, architecture, epics, stories, and UX artifacts are complete and aligned. Run a planning review to inventory documents, map PRD requirements to stories, and flag missing items before Phase 4 development begins.

How do I trace functional requirements from PRD to epics and stories?

Requirements traceability maps functional and non-functional requirements extracted from the PRD directly to epics and stories. This process reveals coverage gaps and ensures every documented requirement has a traceable implementation path before coding starts.

What is the best way to find missing or duplicate artifacts during planning reviews?

Finding missing or duplicate artifacts involves systematically inventorying PRD, architecture, epics, and UX files. A document discovery process identifies duplicates and missing planning items, producing a consolidated readiness report that highlights gaps.

How do I validate UX and architecture alignment for planned epics?

Validating UX and architecture alignment assesses whether planned epics and stories have the necessary architectural support and UX assets. Quality checks evaluate forward dependencies and flag alignment issues to reduce the risk of missed requirements.

When do I need an implementation-readiness report for my project?

An implementation-readiness report is needed prior to Phase 4 implementation to ensure planning documents are complete. It assesses epic and story quality, maps PRD coverage, and surfaces critical gaps that block development.