BMAD-METHOD/expansion-packs/bmad-infrastructure-devops/data/bmad-kb.md

BMad Infrastructure DevOps Expansion Pack Knowledge Base

Overview

The BMad Infrastructure DevOps expansion pack extends the BMad Method framework with comprehensive infrastructure and DevOps capabilities. It enables teams to design, implement, validate, and maintain modern cloud-native infrastructure alongside their application development efforts.

Version: 1.7.0
BMad Compatibility: v4+
Author: Brian (BMad)

Core Purpose

This expansion pack addresses the critical need for systematic infrastructure planning and implementation in modern software projects. It provides:

• Structured approach to infrastructure architecture design
• Platform engineering implementation guidance
• Comprehensive validation and review processes
• Integration with core BMad development workflows
• Support for cloud-native and traditional infrastructure patterns

When to Use This Expansion Pack

Use the BMad Infrastructure DevOps expansion pack when your project involves:

• Cloud Infrastructure Design: AWS, Azure, GCP, or multi-cloud architectures
• Kubernetes and Container Orchestration: Container platform design and implementation
• Infrastructure as Code: Terraform, CloudFormation, Pulumi implementations
• GitOps Workflows: ArgoCD, Flux, or similar continuous deployment patterns
• Platform Engineering: Building internal developer platforms and self-service capabilities
• Service Mesh Implementation: Istio, Linkerd, or similar service mesh architectures
• DevOps Transformation: Establishing or improving DevOps practices and culture

Key Components

1. DevOps Agent: Alex

Role: DevOps Infrastructure Specialist
Experience: 15+ years in infrastructure and platform engineering

Core Principles:

• Infrastructure as Code (IaC) First
• Automation and Repeatability
• Reliability and Scalability
• Security by Design
• Cost Optimization
• Developer Experience Focus

Commands:

• *help - Display available commands and capabilities
• *chat-mode - Interactive conversation mode for infrastructure discussions
• *create-doc - Generate infrastructure documentation from templates
• *review-infrastructure - Conduct systematic infrastructure review
• *validate-infrastructure - Validate infrastructure against comprehensive checklist
• *checklist - Access the 16-section infrastructure validation checklist
• *exit - Return to normal context

2. Infrastructure Templates

Infrastructure Architecture Template

Purpose: Design comprehensive infrastructure architecture
Key Sections:

• Infrastructure Overview (providers, regions, environments)
• Infrastructure as Code approach and tooling
• Network Architecture with visual diagrams
• Compute Resources planning
• Security Architecture design
• Monitoring and Observability strategy
• CI/CD Pipeline architecture
• Disaster Recovery planning
• BMad Integration points

Platform Implementation Template

Purpose: Implement platform infrastructure based on approved architecture
Key Sections:

• Foundation Infrastructure Layer
• Container Platform (Kubernetes) setup
• GitOps Workflow implementation
• Service Mesh configuration
• Developer Experience Platform
• Security hardening procedures
• Platform validation and testing

3. Tasks

Review Infrastructure Task

Purpose: Systematic infrastructure review process
Features:

• Incremental or rapid assessment modes
• Architectural escalation for complex issues
• Advanced elicitation for deep analysis
• Prioritized findings and recommendations
• Integration with BMad Architecture phase

Validate Infrastructure Task

Purpose: Comprehensive infrastructure validation
Features:

• 16-section validation checklist
• Architecture Design Review Gate
• Compliance percentage tracking
• Remediation planning
• BMad integration assessment

4. Infrastructure Validation Checklist

A comprehensive 16-section checklist covering:

Foundation Infrastructure (Sections 1-12):

1. Security Foundation - IAM, encryption, compliance
2. Infrastructure as Code - Version control, testing, documentation
3. Resilience & High Availability - Multi-AZ, failover, SLAs
4. Backup & Disaster Recovery - Strategies, testing, RTO/RPO
5. Monitoring & Observability - Metrics, logging, alerting
6. Performance & Scalability - Auto-scaling, load testing
7. Infrastructure Operations - Patching, maintenance, runbooks
8. CI/CD Infrastructure - Pipelines, environments, deployments
9. Networking & Connectivity - Architecture, security, DNS
10. Compliance & Governance - Standards, auditing, policies
11. BMad Integration - Agent support, workflow alignment
12. Architecture Documentation - Diagrams, decisions, maintenance

Platform Engineering (Sections 13-16): 13. Container Platform - Kubernetes setup, RBAC, networking 14. GitOps Workflows - Repository structure, deployment patterns 15. Service Mesh - Traffic management, security, observability 16. Developer Experience - Self-service, documentation, tooling

Integration with BMad Flow

Workflow Integration Points

1. After Architecture Phase: Infrastructure design begins after application architecture is defined
2. Parallel to Development: Infrastructure implementation runs alongside application development
3. Before Production: Infrastructure validation gates before production deployment
4. Continuous Operation: Ongoing infrastructure reviews and improvements

Agent Collaboration

• With Architect (Sage): Joint planning sessions, design reviews, architectural alignment
• With Developer (Blake): Platform capabilities, development environment setup
• With Product Manager (Finley): Infrastructure requirements, cost considerations
• With Creator Agents: Infrastructure for creative workflows and asset management

Best Practices

Infrastructure Design

1. Start with Requirements: Understand application needs before designing infrastructure
2. Design for Scale: Plan for 10x growth from day one
3. Security First: Implement defense in depth at every layer
4. Cost Awareness: Balance performance with budget constraints
5. Document Everything: Maintain comprehensive documentation

Implementation Approach

1. Incremental Rollout: Deploy infrastructure in stages with validation gates
2. Automation Focus: Automate repetitive tasks and deployments
3. Testing Strategy: Include infrastructure testing in CI/CD pipelines
4. Monitoring Setup: Implement observability before production
5. Team Training: Ensure team understanding of infrastructure

Validation Process

1. Regular Reviews: Schedule periodic infrastructure assessments
2. Checklist Compliance: Maintain high compliance with validation checklist
3. Performance Baselines: Establish and monitor performance metrics
4. Security Audits: Regular security assessments and penetration testing
5. Cost Optimization: Monthly cost reviews and optimization

Common Use Cases

1. New Project Infrastructure

Scenario: Starting a new cloud-native application
Process:

1. Use Infrastructure Architecture template for design
2. Review with Architect agent
3. Implement using Platform Implementation template
4. Validate with comprehensive checklist
5. Deploy incrementally with monitoring

2. Infrastructure Modernization

Scenario: Migrating legacy infrastructure to cloud
Process:

1. Review existing infrastructure
2. Design target architecture
3. Plan migration phases
4. Implement with validation gates
5. Monitor and optimize

3. Platform Engineering Initiative

Scenario: Building internal developer platform
Process:

1. Assess developer needs
2. Design platform architecture
3. Implement Kubernetes/GitOps foundation
4. Build self-service capabilities
5. Enable developer adoption

4. Multi-Cloud Strategy

Scenario: Implementing multi-cloud architecture
Process:

1. Define cloud strategy and requirements
2. Design cloud-agnostic architecture
3. Implement with IaC abstraction
4. Validate cross-cloud functionality
5. Establish unified monitoring

Advanced Features

GitOps Workflows

• Repository Structure: Organized by environment and application
• Deployment Patterns: Progressive delivery, canary deployments
• Secret Management: External secrets operator integration
• Policy Enforcement: OPA/Gatekeeper for compliance

Service Mesh Capabilities

• Traffic Management: Load balancing, circuit breaking, retries
• Security: mTLS, authorization policies
• Observability: Distributed tracing, service maps
• Multi-Cluster: Cross-cluster communication

Developer Self-Service

• Portal Features: Resource provisioning, environment management
• API Gateway: Centralized API management
• Documentation: Automated API docs, runbooks
• Tooling: CLI tools, IDE integrations

Troubleshooting Guide

Common Issues

1. Infrastructure Drift

   • Solution: Implement drift detection in IaC pipelines
   • Prevention: Restrict manual changes, enforce GitOps

2. Cost Overruns

   • Solution: Implement cost monitoring and alerts
   • Prevention: Resource tagging, budget limits

3. Performance Problems

   • Solution: Review monitoring data, scale resources
   • Prevention: Load testing, capacity planning

4. Security Vulnerabilities

   • Solution: Immediate patching, security reviews
   • Prevention: Automated scanning, compliance checks

Metrics and KPIs

Infrastructure Metrics

• Availability: Target 99.9%+ uptime
• Performance: Response time < 100ms
• Cost Efficiency: Cost per transaction trending down
• Security: Zero critical vulnerabilities
• Automation: 90%+ automated deployments

Platform Metrics

• Developer Satisfaction: NPS > 50
• Self-Service Adoption: 80%+ platform usage
• Deployment Frequency: Multiple per day
• Lead Time: < 1 hour from commit to production
• MTTR: < 30 minutes for incidents

Future Enhancements

Planned Features

1. AI-Driven Optimization: Automated infrastructure tuning
2. Enhanced Security: Zero-trust architecture templates
3. Edge Computing: Support for edge infrastructure patterns
4. Sustainability: Carbon footprint optimization
5. Advanced Compliance: Industry-specific compliance templates

Integration Roadmap

1. Cloud Provider APIs: Direct integration with AWS, Azure, GCP
2. IaC Tools: Native support for Terraform, Pulumi
3. Monitoring Platforms: Integration with Datadog, New Relic
4. Security Tools: SIEM and vulnerability scanner integration
5. Cost Management: FinOps platform integration

Conclusion

The BMad Infrastructure DevOps expansion pack provides a comprehensive framework for modern infrastructure and platform engineering. By following its structured approach and leveraging the provided tools and templates, teams can build reliable, scalable, and secure infrastructure that accelerates application delivery while maintaining operational excellence.

For support and updates, refer to the main BMad Method documentation or contact the BMad community.