bmad-check-implementation-readiness

Audit PRDs, UX documentation, and epics for implementation readiness.

Updated May 13, 2026
One-click install
npx skills add https://github.com/Markuson/ivo_corr --skill bmad-check-implementation-readiness-markuson
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-check-implementation-readiness
Source: https://github.com/Markuson/ivo_corr/tree/main/.agents/skills/bmad-check-implementation-readiness
Command: npx skills add https://github.com/Markuson/ivo_corr --skill bmad-check-implementation-readiness-markuson

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill addresses the critical gap between high-level product vision and actionable implementation by ensuring that PRDs, UX designs, and epics are fully aligned and complete before development begins.

Core Features & Use Cases

  • Requirements Traceability: Automatically maps Functional Requirements from the PRD to specific epics and stories to identify coverage gaps.
  • Quality Enforcement: Validates that epics deliver user value rather than technical milestones and checks for forward dependencies.
  • Readiness Reporting: Generates a comprehensive assessment report that flags missing documentation, alignment issues, and structural defects in planning.

Quick Start

Invoke the bmad-check-implementation-readiness skill to begin the automated validation of your current project documentation and planning artifacts.

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 starting software development?

Implementation readiness is checked by auditing PRDs, UX documentation, and epic structures for completeness and alignment. This process scans project artifacts to verify requirements traceability, ensuring functional requirements are covered by independent, user-centric epics while flagging technical debt.

What is requirements traceability and how does it map PRDs to epics?

Requirements traceability automatically maps functional requirements from the PRD to specific epics and stories to identify coverage gaps. It ensures every requirement is accounted for in the implementation plan, validating that epics deliver user value rather than just technical milestones.

How do I validate that my epics deliver user value instead of technical milestones?

Validating epic alignment involves systematically scanning project artifacts to check whether epics deliver user value and verifying forward dependencies. This quality enforcement ensures your epics are user-centric and structurally sound before development begins.

Can I use automated validation to find missing documentation in my project planning?

Automated validation generates a comprehensive readiness assessment report that flags missing documentation, alignment issues, and structural defects. It operates by systematically scanning your project artifacts to extract requirements and verify traceability against defined best practices.

What is the best way to align UX designs and PRDs before sprint planning?

Aligning UX designs and PRDs requires auditing the completeness and alignment of both against your epic structures. This ensures full alignment between high-level product vision and actionable implementation, closing the critical gap before development begins.

Why does my development team keep hitting planning gaps and technical debt during sprints?

Planning gaps and technical debt occur when there is a critical gap between high-level product vision and actionable implementation. Validating implementation readiness beforehand flags these structural defects and missing documentation, ensuring full alignment and completeness before development begins.