bmad-check-implementation-readiness

Discover planning documents and assess implementation readiness before development.

1|Updated Dec 22, 2022
One-click install
npx skills add https://github.com/Rinzler78/osmosis-launcher --skill bmad-check-implementation-readiness-rinzler78
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-check-implementation-readiness
Source: https://github.com/Rinzler78/osmosis-launcher/tree/main/.agents/skills/bmad-check-implementation-readiness
Command: npx skills add https://github.com/Rinzler78/osmosis-launcher --skill bmad-check-implementation-readiness-rinzler78

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps teams verify that their product requirements, architecture, epics, stories, and UX artifacts are complete and aligned before implementation begins, reducing rework and missed requirements.

Core Features & Use Cases

  • Document Discovery: Finds whole and sharded planning artifacts and flags duplicates or missing files.
  • Requirements Traceability: Extracts functional and non-functional requirements from the PRD and checks whether epics cover them.
  • Alignment and Quality Review: Evaluates UX alignment, epic structure, dependency hygiene, and overall implementation readiness.
  • Use Case: A product manager preparing for Phase 4 can use this Skill to identify gaps in planning documents and decide whether the project is ready to build.

Quick Start

Ask the assistant to check implementation readiness for the current project documents and produce a readiness report.

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 validation discovers planning documents and assesses completeness by sequentially analyzing PRD, architecture, epic, story, and UX artifacts to identify gaps before building begins.

What is requirements traceability and how does it ensure epic coverage?

Requirements traceability extracts functional and non-functional requirements from the PRD and checks whether epics cover them, ensuring every documented requirement maps to an actionable implementation item.

How do I validate UX alignment with product requirements before implementation?

UX alignment validation evaluates whether UX artifacts match extracted PRD requirements and epic structures, flagging mismatches in the readiness report to prevent design-development disconnects.

What is the best way to discover sharded planning documents and flag missing files?

Document discovery scans the project workspace to find whole and sharded planning artifacts, automatically flagging duplicates or missing files needed for complete implementation readiness assessment.

Can I assess project readiness if my architecture and epic documents are incomplete?

Yes, the readiness check analyzes existing artifacts and produces a final readiness report highlighting specific gaps in architecture, epics, stories, or UX alignment, guiding whether to proceed or remediate.

When should I not use an implementation readiness check?

Implementation readiness checks require sequential analysis of existing PRD, architecture, epic, story, and UX artifacts; if these planning documents do not exist yet, the readiness validation cannot assess traceability or coverage.