From c5a58bef9cc860568409496875e8013ee28cf333 Mon Sep 17 00:00:00 2001 From: DJ Date: Fri, 3 Apr 2026 05:02:38 -0700 Subject: [PATCH] feat: integrate infrastructure/pipeline into readiness checks and epics - Readiness step-01: discover infrastructure.md and pipeline.md - Readiness step-06: validate infrastructure/deployment readiness (IaC strategy, env topology, pipeline stages, deployment strategy) and advise if DevOps documents are missing - Epics step-01: discover infrastructure/pipeline documents and extract INFRA/PIPELINE requirements for story creation Co-Authored-By: Claude Opus 4.6 (1M context) --- .../steps/step-01-document-discovery.md | 17 ++++++-- .../steps/step-06-final-assessment.md | 31 ++++++++++++++ .../steps/step-01-validate-prerequisites.md | 40 +++++++++++++++++++ 3 files changed, 85 insertions(+), 3 deletions(-) diff --git a/src/bmm-skills/3-solutioning/bmad-check-implementation-readiness/steps/step-01-document-discovery.md b/src/bmm-skills/3-solutioning/bmad-check-implementation-readiness/steps/step-01-document-discovery.md index 8b96d332a..74bd7b7d0 100644 --- a/src/bmm-skills/3-solutioning/bmad-check-implementation-readiness/steps/step-01-document-discovery.md +++ b/src/bmm-skills/3-solutioning/bmad-check-implementation-readiness/steps/step-01-document-discovery.md @@ -48,9 +48,10 @@ To discover, inventory, and organize all project documents, identifying duplicat I will: 1. Search for all required documents (PRD, Architecture, Epics, UX) -2. Group sharded documents together -3. Identify any duplicates (whole + sharded versions) -4. Present findings for your confirmation" +2. Search for optional DevOps documents (Infrastructure, Pipeline) +3. Group sharded documents together +4. Identify any duplicates (whole + sharded versions) +5. Present findings for your confirmation" ### 2. Document Search Patterns @@ -76,6 +77,16 @@ Search for each document type using these patterns: - Whole: `{planning_artifacts}/*ux*.md` - Sharded: `{planning_artifacts}/*ux*/index.md` and related files +#### E. Infrastructure Documents (Optional) + +- Whole: `{planning_artifacts}/*infrastructure*.md` +- Sharded: `{planning_artifacts}/*infrastructure*/index.md` and related files + +#### F. Pipeline Documents (Optional) + +- Whole: `{planning_artifacts}/*pipeline*.md` +- Sharded: `{planning_artifacts}/*pipeline*/index.md` and related files + ### 3. Organize Findings For each document type found: diff --git a/src/bmm-skills/3-solutioning/bmad-check-implementation-readiness/steps/step-06-final-assessment.md b/src/bmm-skills/3-solutioning/bmad-check-implementation-readiness/steps/step-06-final-assessment.md index 467864215..14d2f1bf4 100644 --- a/src/bmm-skills/3-solutioning/bmad-check-implementation-readiness/steps/step-06-final-assessment.md +++ b/src/bmm-skills/3-solutioning/bmad-check-implementation-readiness/steps/step-06-final-assessment.md @@ -60,6 +60,37 @@ Check the {outputFile} for sections added by previous steps: - UX Alignment issues - Epic Quality violations +### 2b. Infrastructure and Deployment Readiness (if documents exist) + +If infrastructure.md or pipeline.md were discovered in Step 1, validate operational readiness: + +**Infrastructure Readiness:** + +- IaC strategy defined (tool, state management, module design) +- Environment topology documented (dev, staging, production) +- Secrets management approach decided +- Container strategy defined (if applicable) +- Alignment with Architecture Category 5 decisions + +**Pipeline Readiness:** + +- CI/CD platform selected and pipeline stages designed +- Deployment strategy decided (blue-green, canary, rolling, etc.) +- Rollback procedures documented +- Security scanning integrated into pipeline stages +- Promotion gates defined between environments + +**If infrastructure/pipeline documents are MISSING but Architecture Category 5 includes infrastructure decisions:** + +``` +⚠️ ADVISORY: Architecture includes infrastructure decisions but no dedicated +infrastructure or pipeline documents exist. Consider running the DevOps +workflows (bmad-create-infrastructure, bmad-create-pipeline) before +implementation to ensure deployment readiness. +``` + +Add infrastructure/deployment findings to the assessment report. + ### 3. Add Final Assessment Section Append to {outputFile}: diff --git a/src/bmm-skills/3-solutioning/bmad-create-epics-and-stories/steps/step-01-validate-prerequisites.md b/src/bmm-skills/3-solutioning/bmad-create-epics-and-stories/steps/step-01-validate-prerequisites.md index 91ad17e08..956494dd4 100644 --- a/src/bmm-skills/3-solutioning/bmad-create-epics-and-stories/steps/step-01-validate-prerequisites.md +++ b/src/bmm-skills/3-solutioning/bmad-create-epics-and-stories/steps/step-01-validate-prerequisites.md @@ -69,6 +69,16 @@ Search for required documents using these patterns (sharded means a large docume 1. `{planning_artifacts}/*ux*.md` (whole document) 2. `{planning_artifacts}/*ux*/index.md` (sharded version) +**Infrastructure Document Search (Optional):** + +1. `{planning_artifacts}/*infrastructure*.md` (whole document) +2. `{planning_artifacts}/*infrastructure*/index.md` (sharded version) + +**Pipeline Document Search (Optional):** + +1. `{planning_artifacts}/*pipeline*.md` (whole document) +2. `{planning_artifacts}/*pipeline*/index.md` (sharded version) + Before proceeding, Ask the user if there are any other documents to include for analysis, and if anything found should be excluded. Wait for user confirmation. Once confirmed, create the {planning_artifacts}/epics.md from the ../templates/epics-template.md and in the front matter list the files in the array of `inputDocuments: []`. ### 3. Extract Functional Requirements (FRs) @@ -123,6 +133,36 @@ Review the Architecture document for technical requirements that impact epic and **IMPORTANT**: If a starter template is mentioned in Architecture, note it prominently. This will impact Epic 1 Story 1. +### 5b. Extract Infrastructure and Pipeline Requirements (if documents exist) + +If infrastructure.md or pipeline.md were discovered, extract operational requirements that need implementation stories: + +**From Infrastructure Document, look for:** + +- IaC setup requirements (Terraform modules, CDK stacks, etc.) +- Environment provisioning automation +- Container orchestration setup (Dockerfiles, Helm charts, K8s manifests) +- Secrets management implementation +- Policy-as-code rules + +**From Pipeline Document, look for:** + +- CI/CD pipeline setup requirements (workflow files, pipeline configs) +- Security scanning tool integration +- Deployment automation scripts +- Promotion gate configurations +- Monitoring and alerting setup for pipeline health + +**Format as part of Additional Requirements, prefixed for clarity:** + +``` +- [INFRA] IaC module setup for [environment topology] +- [INFRA] Container orchestration configuration +- [PIPELINE] CI/CD pipeline with [stages] for [platform] +- [PIPELINE] Deployment automation using [strategy] +... +``` + **Format Additional Requirements as:** ```