bmad-check-readiness

Validate PRDs, architecture, and epics for completeness and alignment.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/KatTate/Bmad-for-Replit --skill bmad-check-readiness
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-check-readiness
Source: https://github.com/KatTate/Bmad-for-Replit/tree/main/.agents/skills/bmad-check-readiness
Command: npx skills add https://github.com/KatTate/Bmad-for-Replit --skill bmad-check-readiness

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and scripts (resource) components.

What problem does it solve?

This Skill ensures that Product Requirements Documents (PRDs), Architecture designs, and Epics are thoroughly validated for completeness and alignment before the implementation phase begins, preventing costly rework.

Core Features & Use Cases

  • Adversarial Review: Critically assesses planning documents for gaps and inconsistencies.
  • Phased Workflow: Guides users through a structured 6-step process for readiness validation.
  • Use Case: Before starting development on a new feature, use this skill to confirm that the PRD, architecture, and all associated epics are fully aligned and meet quality standards.

Quick Start

Use the bmad-check-readiness skill to begin the implementation readiness workflow.

Frequently Asked Questions about bmad-check-readiness

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I validate a PRD and architecture for completeness before implementation?

To validate a PRD and architecture, you perform an adversarial review of planning documents to check for gaps and alignment. This readiness check ensures epics meet quality standards before development begins.

What is an adversarial review for epic quality and PRD analysis?

An adversarial review for epic quality and PRD analysis critically assesses planning documents to find inconsistencies and gaps. It validates epic coverage and UX alignment through a structured six-step workflow.

How do I check if my epics fully cover my PRD requirements?

To check if epics cover PRD requirements, run a phased workflow that validates epic coverage against the PRD. This process analyzes document discovery, UX alignment, and epic quality to ensure full traceability.

When should I run a readiness check on my planning documents?

You should run a readiness check on planning documents before starting development on a new feature. Validating PRD, architecture, and epics at this phase prevents costly rework later in the implementation stage.

What steps are required in a solutioning workflow readiness validation?

A solutioning workflow readiness validation requires a strict six-step process: document discovery, PRD analysis, epic coverage validation, UX alignment, epic quality review, and final assessment to confirm implementation readiness.

Can I use an epic review workflow to find gaps in my architecture design?

Yes, an epic review workflow finds gaps in architecture design by validating architecture documents alongside PRDs and epics. It performs an adversarial review to ensure all planning documents are fully aligned.