Agent skill · product strategy · aj-geddes
bmad-readiness-check
SOLUTIONING GATE — validates cohesion across planning artifacts before any implementation begins. Cross-references PRD (or tech-spec), architecture document, and epics/stories for coverage consistency and missing pieces. Returns a verdict of PASS, CONCERNS, or FAIL with specifics. Does NOT touch code. Use when the user says: - "check if we're ready to build" / "are we ready to implement?" - "validate planning" / "gate check" / "readiness check" - "run the solutioning gate" / "check implementation readiness" - "is the architecture complete?" / "do requirements match architecture?" - "sign off on planning" / "planning done, check it" - "validate PRD against architecture" / "cross-reference planning docs" Intents supported: Validate (primary). Track-adaptive: works for Quick Flow (tech-spec + architecture), BMad Method (PRD + architecture + epics), and Enterprise (all of the above + optional security/DevOps addenda).
Why this skill is useful
Adds a specialized validation workflow for planning artifacts that ensures consistency and completeness before implementation, which the AI wouldn't reliably generate on its own.
What it needs
Requires bash installed locally. About 4k tokens when loaded. Last updated 2026-06-20. 471 stars on the source repository.
What this skill does
BMAD Readiness Check "Planning ends here." This skill is the gate between Solutioning and Implementation. It validates that the planning corpus is internally consistent — requirements are covered by architecture, epics trace back to requirements, and nothing critical is missing — before a single line of code is written. The output is a readiness-report.md with a clear PASS / CONCERNS / FAIL verdict and actionable specifics. --- Workflow Use TodoWrite to track: Load Artifacts → Cross-Reference → Quality Checks → Generate Report → Display Verdict. --- Step 1 — Locate Planning Artifacts Run the bundled existence check: The script checks for required artifact files and prints a PASS / CONCERNS / FAIL pre-flight verdict. Read its output; it will also print artifact paths for you to load in Step 2. Default search root is bmad-output/ (or the user-configured outputFolder). If the user supplies a custom path, pass it as the argument. --- Step 2 — Load and Parse Artifacts Read each artifact the script located: Requirements document (PRD or tech-spec): Extract labelled Functional Requirements (FR-001, FR-002 …) or requirement bullets if not labelled. Extract Non-Functional Requirements (NFR-001 … or named sections: Performance, Security, Scalability, Reliability, Maintainability). Note epic count and high-level scope statements. Architecture document: Extract system components and their responsibilities. Locate FR traceability matrix or explicit FR-to-component mappings. Locate NFR coverage sections. Note technology stack decisions and trade-off notes. Epics / stories (if present): Count epics and stories. For each epic, identify which PRD requirement(s) it references. Record a baseline: --- Step 3 — Cross-Reference Checks 3a. FR → Architecture Coverage For each FR, search the architecture document for the FR identifier AND for the subject matter of the requirement. Mark: Covered — FR explicitly addressed, component assigned. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aj-geddes/bmad-readiness-check