ros/BMAD-METHOD
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

expansion-packs

Browse Source
This commit is contained in:
Brian Madison
2025-06-08 16:18:35 -05:00
parent aa3d8eba67
commit 54406fa871
43 changed files with 3487 additions and 422 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
bmad-core/tasks/create-doc-from-template.md
View File

@@ -37,11 +37,11 @@ Confirm with the user their preferred interaction style:
### 4. Template Processing Rules
**CRITICAL: Never display template markup, LLM instructions, or examples to users**
#### CRITICAL: Never display template markup, LLM instructions, or examples to users
- Replace all {{placeholders}} with actual content
- Execute all [[LLM: instructions]] internally
- Process <<REPEAT>> sections as needed
- Process `<<REPEAT>>` sections as needed
- Evaluate ^^CONDITION^^ blocks and include only if applicable
- Use @{examples} for guidance but never output them

147
bmad-core/tasks/infra/create-infrastructure-architecture.md
View File

@@ -1,147 +0,0 @@
# Infrastructure Architecture Creation Task
## Purpose
To design a comprehensive infrastructure architecture that defines all aspects of the technical infrastructure strategy, from cloud platform selection to deployment patterns. This architecture will serve as the definitive blueprint for the DevOps/Platform Engineering team to implement, ensuring consistency, security, and operational excellence across all infrastructure components.
## Inputs
- Product Requirements Document (PRD)
- Main System Architecture Document
- Technology Stack Document (`docs/tech-stack.md`)
- Infrastructure Guidelines (`docs/infrastructure/guidelines.md`)
- Any existing infrastructure documentation
## Key Activities & Instructions
### 1. Confirm Interaction Mode
- Ask the user: "How would you like to proceed with creating the infrastructure architecture? We can work:
A. **Incrementally (Default & Recommended):** We'll go through each architectural decision and document section step-by-step. I'll present drafts, and we'll seek your feedback before moving to the next part. This is best for complex infrastructure designs.
B. **"YOLO" Mode:** I can produce a comprehensive initial draft of the infrastructure architecture for you to review more broadly first. We can then iterate on specific sections based on your feedback."
- Request the user to select their preferred mode and proceed accordingly.
### 2. Gather Infrastructure Requirements
- Review the product requirements document to understand business needs and scale requirements
- Analyze the main system architecture to identify infrastructure dependencies
- Document non-functional requirements (performance, scalability, reliability, security)
- Identify compliance and regulatory requirements affecting infrastructure
- Map application architecture patterns to infrastructure needs
- <critical_rule>Cross-reference with PRD Technical Assumptions to ensure alignment with repository and service architecture decisions</critical_rule>
### 3. Design Infrastructure Architecture Strategy
- **If "Incremental Mode" was selected:**
- For each major infrastructure domain:
- **a. Present Domain Purpose:** Explain what this infrastructure domain provides and its strategic importance
- **b. Present Strategic Options:** Provide 2-3 viable approaches with architectural pros and cons
- **c. Make Strategic Recommendation:** Recommend the best approach with clear architectural rationale
- **d. Incorporate Feedback:** Discuss with user and iterate based on feedback
- **e. [Offer Advanced Self-Refinement & Elicitation Options](#offer-advanced-self-refinement--elicitation-options)**
- **f. Document Architectural Decision:** Record the final strategic choice with justification
- **If "YOLO Mode" was selected:**
- Design strategic approaches for all major infrastructure domains
- Document architectural decisions and rationales
- Present comprehensive infrastructure strategy for review
- Iterate based on feedback
### 4. Document Infrastructure Architecture Blueprint
- Populate all sections of the infrastructure architecture template:
- **Cloud Strategy & Platform Selection** - Multi-cloud vs single cloud, platform rationale
- **Network Architecture Patterns** - VPC design, connectivity strategies, security zones
- **Compute Architecture Strategy** - Container vs serverless vs VM strategies, scaling patterns
- **Data Architecture & Storage Strategy** - Database selection, data tier strategies, backup approaches
- **Security Architecture Framework** - Zero-trust patterns, identity strategies, encryption approaches
- **Observability Architecture** - Monitoring strategies, logging patterns, alerting frameworks
- **CI/CD Architecture Patterns** - Pipeline strategies, deployment patterns, environment promotion
- **Disaster Recovery Architecture** - RTO/RPO strategies, failover patterns, business continuity
- **Cost Optimization Framework** - Resource optimization strategies, cost allocation patterns
- **Environment Strategy** - Dev/staging/prod patterns, environment isolation approaches
- **Infrastructure Evolution Strategy** - Technology migration paths, scaling roadmaps
- **Cross-team Collaboration Model** - Integration with development teams, handoff protocols
### 5. Implementation Feasibility Review & Collaboration
- **Architect → DevOps/Platform Feedback Loop:**
- Present architectural blueprint summary to DevOps/Platform Engineering Agent for feasibility review
- Request specific feedback on:
- **Operational Complexity:** Are the proposed patterns implementable with current tooling and expertise?
- **Resource Constraints:** Do infrastructure requirements align with available resources and budgets?
- **Security Implementation:** Are security patterns achievable with current security toolchain?
- **Operational Overhead:** Will the proposed architecture create excessive operational burden?
- **Technology Constraints:** Are selected technologies compatible with existing infrastructure?
- Document all feasibility feedback and concerns raised by DevOps/Platform Engineering Agent
- Iterate on architectural decisions based on operational constraints and feedback
- <critical_rule>Address all critical feasibility concerns before proceeding to final architecture documentation</critical_rule>
### 6. Create Infrastructure Architecture Diagrams
- Develop high-level infrastructure strategy diagrams using Mermaid
- Create network topology architecture diagrams
- Document data flow and integration architecture diagrams
- Illustrate deployment pipeline architecture patterns
- Visualize environment relationship and promotion strategies
- Design security architecture and trust boundary diagrams
### 7. Define Implementation Handoff Strategy
- Create clear specifications for DevOps/Platform Engineering implementation
- Define architectural constraints and non-negotiable requirements
- Specify technology selections with version requirements where critical
- Document architectural patterns that must be followed during implementation
- Create implementation validation criteria
- Prepare architectural decision records (ADRs) for key infrastructure choices
### 8. BMAD Integration Architecture
- Design infrastructure architecture to support other BMAD agents:
- **Development Environment Architecture** - Local development patterns, testing infrastructure
- **Deployment Architecture** - How applications from Frontend/Backend agents will be deployed
- **Integration Architecture** - How infrastructure supports cross-service communication
- Document infrastructure requirements for each BMAD agent workflow
### 9. Architecture Review and Finalization
- Review architecture against system architecture for alignment
- Validate infrastructure architecture supports all application requirements
- Ensure architectural decisions are implementable within project constraints
- Address any architectural gaps or inconsistencies
- Prepare comprehensive architecture handoff documentation for implementation team
## Output
A comprehensive infrastructure architecture document that provides:
1. **Strategic Infrastructure Blueprint** - High-level architecture strategy and patterns
2. **Technology Selection Rationale** - Justified technology choices and architectural decisions
3. **Implementation Specifications** - Clear guidance for DevOps/Platform Engineering implementation
4. **Architectural Constraints** - Non-negotiable requirements and patterns
5. **Integration Architecture** - How infrastructure supports application architecture
6. **BMAD Workflow Support** - Infrastructure architecture supporting all agent workflows
7. **Feasibility Validation** - Documented operational feedback and constraint resolution
**Output file**: `docs/infrastructure-architecture.md`
## Offer Advanced Self-Refinement & Elicitation Options
Present the user with the following list of 'Advanced Reflective, Elicitation & Brainstorming Actions'. Explain that these are optional steps to help ensure quality, explore alternatives, and deepen the understanding of the current section before finalizing it and moving on. The user can select an action by number, or choose to skip this and proceed to finalize the section.
"To ensure the quality of the current section: **[Specific Section Name]** and to ensure its robustness, explore alternatives, and consider all angles, I can perform any of the following actions. Please choose a number (8 to finalize and proceed):
**Advanced Reflective, Elicitation & Brainstorming Actions I Can Take:**
1. **Alternative Architecture Strategy Evaluation**
2. **Scalability & Performance Architecture Stress Test (Theoretical)**
3. **Security Architecture & Compliance Deep Dive**
4. **Cost Architecture Analysis & Optimization Strategy Review**
5. **Operational Excellence & Reliability Architecture Assessment**
6. **Cross-Functional Integration & BMAD Workflow Analysis**
7. **Future Technology & Migration Architecture Path Exploration**
8. **Finalize this Section and Proceed.**
After I perform the selected action, we can discuss the outcome and decide on any further revisions for this section."
REPEAT by Asking the user if they would like to perform another Reflective, Elicitation & Brainstorming Action UNTIL the user indicates it is time to proceed to the next section (or selects #8)

232
bmad-core/tasks/infra/create-platform-infrastructure.md
View File

@@ -1,232 +0,0 @@
# Platform Infrastructure Implementation Task
## Purpose
To implement a comprehensive platform infrastructure stack based on the Infrastructure Architecture Document, including foundation infrastructure, container orchestration, GitOps workflows, service mesh, and developer experience platforms. This integrated approach ensures all platform components work synergistically to provide a complete, secure, and operationally excellent platform foundation.
## Inputs
- **Infrastructure Architecture Document** (`docs/infrastructure-architecture.md` - from Architect Agent)
- Infrastructure Change Request (`docs/infrastructure/{ticketNumber}.change.md`)
- Infrastructure Guidelines (`docs/infrastructure/guidelines.md`)
- Technology Stack Document (`docs/tech-stack.md`)
- `infrastructure-checklist.md` (for validation)
## Key Activities & Instructions
### 1. Confirm Interaction Mode
- Ask the user: "How would you like to proceed with platform infrastructure implementation? We can work:
A. **Incrementally (Default & Recommended):** We'll implement each platform layer step-by-step (Foundation → Container Platform → GitOps → Service Mesh → Developer Experience), validating integration at each stage. This ensures thorough testing and operational readiness.
B. **"YOLO" Mode:** I'll implement the complete platform stack in logical groups, with validation at major integration milestones. This is faster but requires comprehensive end-to-end testing."
- Request the user to select their preferred mode and proceed accordingly.
### 2. Architecture Review & Implementation Planning
- Review Infrastructure Architecture Document for complete platform specifications
- Validate platform requirements against application architecture and business needs
- Create integrated implementation roadmap with proper dependency sequencing
- Plan resource allocation, security policies, and operational procedures across all platform layers
- Document rollback procedures and risk mitigation strategies for the entire platform
- <critical_rule>Verify the infrastructure change request is approved before beginning implementation. If not, HALT and inform the user.</critical_rule>
### 3. Joint Implementation Planning Session
- **Architect ↔ DevOps/Platform Collaborative Planning:**
- **Architecture Alignment Review:**
- Confirm understanding of architectural decisions and rationale with Architect Agent
- Validate interpretation of infrastructure architecture document
- Clarify any ambiguous or unclear architectural specifications
- Document agreed-upon implementation approach for each architectural component
- **Implementation Strategy Collaboration:**
- **Technology Implementation Planning:** Collaborate on specific technology versions, configurations, and deployment patterns
- **Security Implementation Planning:** Align on security control implementation approach and validation methods
- **Integration Planning:** Plan component integration sequence and validation checkpoints
- **Operational Considerations:** Discuss operational patterns, monitoring strategies, and maintenance approaches
- **Resource Planning:** Confirm resource allocation, sizing, and optimization strategies
- **Risk & Constraint Discussion:**
- Identify potential implementation risks and mitigation strategies
- Document operational constraints that may impact architectural implementation
- Plan contingency approaches for high-risk implementation areas
- Establish escalation triggers for implementation issues requiring architectural input
- **Implementation Validation Planning:**
- Define validation criteria for each platform component and integration point
- Plan testing strategies and acceptance criteria with Architect input
- Establish quality gates and review checkpoints throughout implementation
- Document success metrics and performance benchmarks
- **Documentation & Knowledge Transfer Planning:**
- Plan documentation approach and knowledge transfer requirements
- Define operational runbooks and troubleshooting guide requirements
- Establish ongoing collaboration points for implementation support
- <critical_rule>Complete joint planning session before beginning platform implementation. Document all planning outcomes and agreements.</critical_rule>
### 4. Foundation Infrastructure Implementation
- **If "Incremental Mode" was selected:**
- **a. Foundation Infrastructure Setup:**
- Present foundation infrastructure scope and its role in the platform stack
- Implement core cloud resources, networking, storage, and security foundations
- Configure basic monitoring, logging, and operational tooling
- Validate foundation readiness for platform components
- [Offer Advanced Self-Refinement & Elicitation Options](#offer-advanced-self-refinement--elicitation-options)
- **If "YOLO Mode" was selected:**
- Implement complete foundation infrastructure per architecture specifications
- Prepare foundation for all platform components simultaneously
### 5. Container Platform Implementation
- **If "Incremental Mode" was selected:**
- **b. Container Orchestration Platform:**
- Present container platform scope and integration with foundation infrastructure
- Install and configure container orchestration platform (Kubernetes/AKS/EKS/GKE)
- Implement RBAC, security policies, and resource management
- Configure networking, storage classes, and operational tooling
- Validate container platform functionality and readiness for applications
- [Offer Advanced Self-Refinement & Elicitation Options](#offer-advanced-self-refinement--elicitation-options)
- **If "YOLO Mode" was selected:**
- Deploy complete container platform integrated with foundation infrastructure
### 6. GitOps Workflows Implementation
- **If "Incremental Mode" was selected:**
- **c. GitOps Configuration Management:**
- Present GitOps scope and integration with container platform
- Implement GitOps operators and configuration management systems
- Configure repository structures, sync policies, and environment promotion
- Set up policy enforcement and drift detection
- Validate GitOps workflows and configuration management
- [Offer Advanced Self-Refinement & Elicitation Options](#offer-advanced-self-refinement--elicitation-options)
- **If "YOLO Mode" was selected:**
- Deploy complete GitOps stack integrated with container and foundation platforms
### 7. Service Mesh Implementation
- **If "Incremental Mode" was selected:**
- **d. Service Communication Platform:**
- Present service mesh scope and integration with existing platform layers
- Install and configure service mesh control and data planes
- Implement traffic management, security policies, and observability
- Configure service discovery, load balancing, and communication policies
- Validate service mesh functionality and inter-service communication
- [Offer Advanced Self-Refinement & Elicitation Options](#offer-advanced-self-refinement--elicitation-options)
- **If "YOLO Mode" was selected:**
- Deploy complete service mesh integrated with all platform components
### 8. Developer Experience Platform Implementation
- **If "Incremental Mode" was selected:**
- **e. Developer Experience Platform:**
- Present developer platform scope and integration with complete platform stack
- Implement developer portals, self-service capabilities, and golden path templates
- Configure platform APIs, automation workflows, and productivity tooling
- Set up developer onboarding and documentation systems
- Validate developer experience and workflow integration
- [Offer Advanced Self-Refinement & Elicitation Options](#offer-advanced-self-refinement--elicitation-options)
- **If "YOLO Mode" was selected:**
- Deploy complete developer experience platform integrated with all infrastructure
### 9. Platform Integration & Security Hardening
- Implement end-to-end security policies across all platform layers
- Configure integrated monitoring and observability for the complete platform stack
- Set up platform-wide backup, disaster recovery, and business continuity procedures
- Implement cost optimization and resource management across all platform components
- Configure platform-wide compliance monitoring and audit logging
- Validate complete platform security posture and operational readiness
### 10. Platform Operations & Automation
- Set up comprehensive platform monitoring, alerting, and operational dashboards
- Implement automated platform maintenance, updates, and lifecycle management
- Configure platform health checks, performance optimization, and capacity planning
- Set up incident response procedures and operational runbooks for the complete platform
- Implement platform SLA monitoring and service level management
- Validate operational excellence and platform reliability
### 11. BMAD Workflow Integration
- Verify complete platform supports all BMAD agent workflows:
- **Frontend/Backend Development** - Test complete application development and deployment workflows
- **Infrastructure Development** - Validate infrastructure-as-code development and deployment
- **Cross-Agent Collaboration** - Ensure seamless collaboration between all agent types
- **CI/CD Integration** - Test complete continuous integration and deployment pipelines
- **Monitoring & Observability** - Verify complete application and infrastructure monitoring
- Document comprehensive integration verification results and workflow optimizations
### 12. Platform Validation & Knowledge Transfer
- Execute comprehensive platform testing with realistic workloads and scenarios
- Validate against all sections of infrastructure checklist for complete platform
- Perform security scanning, compliance verification, and performance testing
- Test complete platform disaster recovery and resilience procedures
- Complete comprehensive knowledge transfer to operations and development teams
- Document complete platform configuration, operational procedures, and troubleshooting guides
- <critical_rule>Update infrastructure change request status to reflect completion</critical_rule>
### 13. Implementation Review & Architect Collaboration
- **Post-Implementation Collaboration with Architect:**
- **Implementation Validation Review:**
- Present implementation outcomes against architectural specifications
- Document any deviations from original architecture and rationale
- Validate that implemented platform meets architectural intent and requirements
- **Lessons Learned & Architecture Feedback:**
- Provide feedback to Architect Agent on implementation experience
- Document implementation challenges and successful patterns
- Recommend architectural improvements for future implementations
- Share operational insights that could influence future architectural decisions
- **Knowledge Transfer & Documentation Review:**
- Review operational documentation with Architect for completeness and accuracy
- Ensure architectural decisions are properly documented in operational guides
- Plan ongoing collaboration for platform evolution and maintenance
- Document collaboration outcomes and recommendations for future architecture-implementation cycles
### 14. Platform Handover & Continuous Improvement
- Establish platform monitoring and continuous improvement processes
- Set up feedback loops with development teams and platform users
- Plan platform evolution roadmap and technology upgrade strategies
- Implement platform metrics and KPI tracking for operational excellence
- Create platform governance and change management procedures
- Establish platform support and maintenance responsibilities
## Output
Fully operational and integrated platform infrastructure with:
1. **Complete Foundation Infrastructure** - Cloud resources, networking, storage, and security foundations
2. **Production-Ready Container Platform** - Orchestration with proper security, monitoring, and resource management
3. **Operational GitOps Workflows** - Version-controlled operations with automated sync and policy enforcement
4. **Service Mesh Communication Platform** - Advanced service communication with security and observability
5. **Developer Experience Platform** - Self-service capabilities with productivity tooling and golden paths
6. **Integrated Platform Operations** - Comprehensive monitoring, automation, and operational excellence
7. **BMAD Workflow Support** - Verified integration supporting all agent development and deployment patterns
8. **Platform Documentation** - Complete operational guides, troubleshooting resources, and developer documentation
9. **Joint Planning Documentation** - Collaborative planning outcomes and architectural alignment records
10. **Implementation Review Results** - Post-implementation validation and architect collaboration outcomes
## Offer Advanced Self-Refinement & Elicitation Options
Present the user with the following list of 'Advanced Reflective, Elicitation & Brainstorming Actions'. Explain that these are optional steps to help ensure quality, explore alternatives, and deepen the understanding of the current platform layer before finalizing it and moving to the next. The user can select an action by number, or choose to skip this and proceed.
"To ensure the quality of the current platform layer: **[Specific Platform Layer Name]** and to ensure its robustness, explore alternatives, and consider all angles, I can perform any of the following actions. Please choose a number (8 to finalize and proceed):
**Advanced Reflective, Elicitation & Brainstorming Actions I Can Take:**
1. **Platform Layer Security Hardening & Integration Review**
2. **Performance Optimization & Resource Efficiency Analysis**
3. **Operational Excellence & Automation Enhancement**
4. **Platform Integration & Dependency Validation**
5. **Developer Experience & Workflow Optimization**
6. **Disaster Recovery & Platform Resilience Testing (Theoretical)**
7. **BMAD Agent Workflow Integration & Cross-Platform Testing**
8. **Finalize this Platform Layer and Proceed.**
After I perform the selected action, we can discuss the outcome and decide on any further improvements for this platform layer."
REPEAT by Asking the user if they would like to perform another Reflective, Elicitation & Brainstorming Action UNTIL the user indicates it is time to proceed to the next platform layer (or selects #8)