bmad-check-implementation-readiness

Verify completeness and consistency of PRD, architecture, epics, and UX documents.

2|2|Updated Feb 16, 2025
One-click install
npx skills add https://github.com/allaydesai/Trading-ntrader --skill bmad-check-implementation-readiness-allaydesai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-check-implementation-readiness
Source: https://github.com/allaydesai/Trading-ntrader/tree/main/.cursor/skills/bmad-check-implementation-readiness
Command: npx skills add https://github.com/allaydesai/Trading-ntrader --skill bmad-check-implementation-readiness-allaydesai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps product teams verify that PRD, architecture, epics, and UX documents are fully complete and well-structured before moving into implementation phases.

Core Features & Use Cases

  • Requirements Validation: Checks completeness of PRD, architecture, and user stories.
  • Workflow Guidance: Guides product managers through a sequential, step-by-step validation process.
  • Use Case: When preparing for product development, use this Skill to ensure all planning artifacts are aligned, eliminating gaps and ambiguities.

Quick Start

Initiate the validation process by confirming the completeness of your project documentation, then proceed step-by-step through the 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 verify project documentation is complete before development?

To verify project documentation completeness, systematically check that your PRD, architecture, epics, and UX specs are consistent and fully structured. This validation eliminates gaps and ambiguities, ensuring all artifacts are prepared for efficient implementation.

What is the best way to check PRD and architecture alignment for product development?

Checking PRD and architecture alignment requires a sequential, step-by-step validation workflow. You inspect requirements, architectural documents, and user stories to ensure all planning artifacts are structured consistently before entering the implementation phase.

How do I validate requirements and user stories for implementation readiness?

Validating requirements and user stories involves a thorough document inspection process that checks for completeness and consistency across epics and UX documents. This ensures all specifications are strictly reviewed and prepared before development begins.

When do I need to perform a pre-development review of specifications?

You need a pre-development review of specifications during the planning phase before any implementation begins. This process ensures your project documentation, including PRD and architecture, is fully complete and aligned to prevent development gaps.

Can I use a sequential validation process for UX and epics documentation?

Yes, you can use a sequential validation process to inspect UX and epics documentation. Strict adherence to these sequential validation steps ensures all specifications are thoroughly reviewed for completeness and consistency before implementation.