bmad-check-implementation-readiness

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

4|1|Updated Sep 30, 2024

Search Tags:#product-management #planning-workflow #requirements-traceability #ux-alignment #prd-validation #implementation-readiness #epic-quality

Ready to run

npx skills add https://github.com/co-cddo/ndx --skill bmad-check-implementation-readiness-co-cddo

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: bmad-check-implementation-readiness
Source: https://github.com/co-cddo/ndx/tree/main/_bmad/bmm/3-solutioning/bmad-check-implementation-readiness
Command: npx skills add https://github.com/co-cddo/ndx --skill bmad-check-implementation-readiness-co-cddo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validates that PRD, UX, Architecture and Epics specs are complete and aligned to ensure a smooth readiness review before implementation.

Core Features & Use Cases

Verifies that planning artifacts (PRD, Architecture, Epics and Stories) are complete and consistent.
Highlights gaps, dependencies, and risks to prevent rework during development.
Provides a structured readiness workflow with traceability from PRD requirements to implemented epics.

Quick Start

Follow the workflow in ./workflow.md to begin the readiness verification process.

Frequently Asked Questions about bmad-check-implementation-readiness

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

FAQPage Schema

What is implementation readiness in software project planning?▼

Implementation readiness validates that PRD, UX, Architecture, and Epics are complete and aligned to ensure a smooth review before development begins. It highlights gaps, dependencies, and risks to prevent rework during the implementation phase.

How do I validate PRD and Epic alignment before development?▼

Validate PRD and Epic alignment by applying a structured readiness workflow that verifies planning artifact consistency. This process highlights gaps and ensures traceability from PRD requirements directly down to implemented epics and stories.

Does this readiness workflow check UX and architecture consistency?▼

Yes, the readiness workflow checks UX and architecture consistency by verifying that planning artifacts are complete. It guides reviews of PRD content and architecture alignment to enforce a consistent readiness workflow before development starts.

What is the best way to ensure traceability from PRD requirements to epics?▼

The best way to ensure traceability is to use a validation workflow that enforces traceability from PRD requirements to epics and stories. This structured approach identifies dependencies and risks early, ensuring epic quality before implementation.

How do I identify gaps in product requirements and architecture specs?▼

Identify gaps in product requirements and architecture specs by running a readiness verification process. This workflow validates PRD content and architecture alignment, highlighting missing dependencies and risks to prevent development rework.

When should I run an implementation readiness check on my planning artifacts?▼

Run an implementation readiness check immediately before development begins to validate that PRD, UX, Architecture, and Epic specs are complete. This prevents rework by highlighting gaps, dependencies, and risks across all planning artifacts.