bmad-check-implementation-readiness

Validate PRD, Architecture, Epics, and UX specs for implementation readiness.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validates that PRD, Architecture, Epics, and UX specs are complete, ensuring no gaps before starting implementation.

Core Features & Use Cases

  • Stepwise validation of planning artifacts to surface gaps and misalignments.
  • Enforced sequential workflow with frontmatter-based state tracking for auditability.
  • Actionable remediation guidance to align artifacts prior to development.

Quick Start

Run the skill and say "check implementation readiness" to start the guided workflow.

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 for PRD, Architecture, and Epic planning artifacts?

To check implementation readiness, this skill automates the orchestration and validation of planning artifacts to ensure complete consistency and traceability before coding begins.

What's the best way to validate PRD and UX spec alignment before a major release?

Validating PRD and UX spec alignment before a major release requires a stepwise validation workflow that surfaces gaps and misalignments, providing actionable remediation guidance to align artifacts prior to development.

How does state tracking work for sequential workflow validation of product planning artifacts?

State tracking for sequential workflow validation uses frontmatter to enforce a strict stepwise process, maintaining auditability and ensuring mandatory validation is completed before moving to the next phase.

Can I use this readiness validation workflow for new feature development preparation?

Yes, this readiness validation workflow applies to product teams preparing for new features and major releases, ensuring traceability and gap remediation across PRD, Architecture, Epics, and UX specs.

Why does implementation readiness validation require a strict stepwise workflow?

Implementation readiness validation requires a strict stepwise workflow because it enforces mandatory validation and state tracking to systematically surface issues and gaps before any coding begins.

What problem does validating planning artifacts solve for product teams?

Validating planning artifacts solves the problem of incomplete PRD, Architecture, Epics, and UX specs, ensuring no gaps exist before starting implementation and reducing downstream development risks.