appiq-solution 1.3.3 → 1.4.3

package/#Tools/APPIQ-METHOD/deployment/build/expansion-packs/bmad-infrastructure-devops/data/bmad-kb.md

@@ -1,308 +0,0 @@
-# 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.

package/#Tools/APPIQ-METHOD/deployment/build/expansion-packs/bmad-infrastructure-devops/tasks/review-infrastructure.md

@@ -1,160 +0,0 @@
-# Infrastructure Review Task
-
-## Purpose
-
-To conduct a thorough review of existing infrastructure to identify improvement opportunities, security concerns, and alignment with best practices. This task helps maintain infrastructure health, optimize costs, and ensure continued alignment with organizational requirements.
-
-## Inputs
-
-- Current infrastructure documentation
-- Monitoring and logging data
-- Recent incident reports
-- Cost and performance metrics
-- `infrastructure-checklist.md` (primary review framework)
-
-## Key Activities & Instructions
-
-### 1. Confirm Interaction Mode
-
-- Ask the user: "How would you like to proceed with the infrastructure review? We can work:
-  A. **Incrementally (Default & Recommended):** We'll work through each section of the checklist methodically, documenting findings for each item before moving to the next section. This provides a thorough review.
-  B. **"YOLO" Mode:** I can perform a rapid assessment of all infrastructure components and present a comprehensive findings report. This is faster but may miss nuanced details."
-- Request the user to select their preferred mode and proceed accordingly.
-
-### 2. Prepare for Review
-
-- Gather and organize current infrastructure documentation
-- Access monitoring and logging systems for operational data
-- Review recent incident reports for recurring issues
-- Collect cost and performance metrics
-- <critical_rule>Establish review scope and boundaries with the user before proceeding</critical_rule>
-
-### 3. Conduct Systematic Review
-
-- **If "Incremental Mode" was selected:**
-
-  - For each section of the infrastructure checklist:
-    - **a. Present Section Focus:** Explain what aspects of infrastructure this section reviews
-    - **b. Work Through Items:** Examine each checklist item against current infrastructure
-    - **c. Document Current State:** Record how current implementation addresses or fails to address each item
-    - **d. Identify Gaps:** Document improvement opportunities with specific recommendations
-    - **e. [Offer Advanced Self-Refinement & Elicitation Options](#offer-advanced-self-refinement--elicitation-options)**
-    - **f. Section Summary:** Provide an assessment summary before moving to the next section
-
-- **If "YOLO Mode" was selected:**
-  - Rapidly assess all infrastructure components
-  - Document key findings and improvement opportunities
-  - Present a comprehensive review report
-  - <important_note>After presenting the full review in YOLO mode, you MAY still offer the 'Advanced Reflective & Elicitation Options' menu for deeper investigation of specific areas with issues.</important_note>
-
-### 4. Generate Findings Report
-
-- Summarize review findings by category (Security, Performance, Cost, Reliability, etc.)
-- Prioritize identified issues (Critical, High, Medium, Low)
-- Document recommendations with estimated effort and impact
-- Create an improvement roadmap with suggested timelines
-- Highlight cost optimization opportunities
-
-### 5. BMad Integration Assessment
-
-- Evaluate how current infrastructure supports other BMad agents:
-  - **Development Support:** Assess how infrastructure enables Frontend Dev (Mira), Backend Dev (Enrique), and Full Stack Dev workflows
-  - **Product Alignment:** Verify infrastructure supports PRD requirements from Product Owner (Oli)
-  - **Architecture Compliance:** Check if implementation follows Architect (Alphonse) decisions
-  - Document any gaps in BMad integration
-
-### 6. Architectural Escalation Assessment
-
-- **DevOps/Platform → Architect Escalation Review:**
-  - Evaluate review findings for issues requiring architectural intervention:
-    - **Technical Debt Escalation:**
-      - Identify infrastructure technical debt that impacts system architecture
-      - Document technical debt items that require architectural redesign vs. operational fixes
-      - Assess cumulative technical debt impact on system maintainability and scalability
-    - **Performance/Security Issue Escalation:**
-      - Identify performance bottlenecks that require architectural solutions (not just operational tuning)
-      - Document security vulnerabilities that need architectural security pattern changes
-      - Assess capacity and scalability issues requiring architectural scaling strategy revision
-    - **Technology Evolution Escalation:**
-      - Identify outdated technologies that need architectural migration planning
-      - Document new technology opportunities that could improve system architecture
-      - Assess technology compatibility issues requiring architectural integration strategy changes
-  - **Escalation Decision Matrix:**
-    - **Critical Architectural Issues:** Require immediate Architect Agent involvement for system redesign
-    - **Significant Architectural Concerns:** Recommend Architect Agent review for potential architecture evolution
-    - **Operational Issues:** Can be addressed through operational improvements without architectural changes
-    - **Unclear/Ambiguous Issues:** When escalation level is uncertain, consult with user for guidance and decision
-  - Document escalation recommendations with clear justification and impact assessment
-  - <critical_rule>If escalation classification is unclear or ambiguous, HALT and ask user for guidance on appropriate escalation level and approach</critical_rule>
-
-### 7. Present and Plan
-
-- Prepare an executive summary of key findings
-- Create detailed technical documentation for implementation teams
-- Develop an action plan for critical and high-priority items
-- **Prepare Architectural Escalation Report** (if applicable):
-  - Document all findings requiring Architect Agent attention
-  - Provide specific recommendations for architectural changes or reviews
-  - Include impact assessment and priority levels for architectural work
-  - Prepare escalation summary for Architect Agent collaboration
-- Schedule follow-up reviews for specific areas
-- <important_note>Present findings in a way that enables clear decision-making on next steps and escalation needs.</important_note>
-
-### 8. Execute Escalation Protocol
-
-- **If Critical Architectural Issues Identified:**
-  - **Immediate Escalation to Architect Agent:**
-    - Present architectural escalation report with critical findings
-    - Request architectural review and potential redesign for identified issues
-    - Collaborate with Architect Agent on priority and timeline for architectural changes
-    - Document escalation outcomes and planned architectural work
-- **If Significant Architectural Concerns Identified:**
-  - **Scheduled Architectural Review:**
-    - Prepare detailed technical findings for Architect Agent review
-    - Request architectural assessment of identified concerns
-    - Schedule collaborative planning session for potential architectural evolution
-    - Document architectural recommendations and planned follow-up
-- **If Only Operational Issues Identified:**
-  - Proceed with operational improvement planning without architectural escalation
-  - Monitor for future architectural implications of operational changes
-- **If Unclear/Ambiguous Escalation Needed:**
-  - **User Consultation Required:**
-    - Present unclear findings and escalation options to user
-    - Request user guidance on appropriate escalation level and approach
-    - Document user decision and rationale for escalation approach
-    - Proceed with user-directed escalation path
-- <critical_rule>All critical architectural escalations must be documented and acknowledged by Architect Agent before proceeding with implementation</critical_rule>
-
-## Output
-
-A comprehensive infrastructure review report that includes:
-
-1. **Current state assessment** for each infrastructure component
-2. **Prioritized findings** with severity ratings
-3. **Detailed recommendations** with effort/impact estimates
-4. **Cost optimization opportunities**
-5. **BMad integration assessment**
-6. **Architectural escalation assessment** with clear escalation recommendations
-7. **Action plan** for critical improvements and architectural work
-8. **Escalation documentation** for Architect Agent collaboration (if applicable)
-
-## 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. **Root Cause Analysis & Pattern Recognition**
-2. **Industry Best Practice Comparison**
-3. **Future Scalability & Growth Impact Assessment**
-4. **Security Vulnerability & Threat Model Analysis**
-5. **Operational Efficiency & Automation Opportunities**
-6. **Cost Structure Analysis & Optimization Strategy**
-7. **Compliance & Governance Gap Assessment**
-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)

package/#Tools/APPIQ-METHOD/deployment/build/expansion-packs/bmad-infrastructure-devops/tasks/validate-infrastructure.md

@@ -1,154 +0,0 @@
-# Infrastructure Validation Task
-
-## Purpose
-
-To comprehensively validate platform infrastructure changes against security, reliability, operational, and compliance requirements before deployment. This task ensures all platform infrastructure meets organizational standards, follows best practices, and properly integrates with the broader BMad ecosystem.
-
-## Inputs
-
-- Infrastructure Change Request (`docs/infrastructure/{ticketNumber}.change.md`)
-- **Infrastructure Architecture Document** (`docs/infrastructure-architecture.md` - from Architect Agent)
-- Infrastructure Guidelines (`docs/infrastructure/guidelines.md`)
-- Technology Stack Document (`docs/tech-stack.md`)
-- `infrastructure-checklist.md` (primary validation framework - 16 comprehensive sections)
-
-## Key Activities & Instructions
-
-### 1. Confirm Interaction Mode
-
-- Ask the user: "How would you like to proceed with platform infrastructure validation? We can work:
-  A. **Incrementally (Default & Recommended):** We'll work through each section of the checklist step-by-step, documenting compliance or gaps for each item before moving to the next section. This is best for thorough validation and detailed documentation of the complete platform stack.
-  B. **"YOLO" Mode:** I can perform a rapid assessment of all checklist items and present a comprehensive validation report for review. This is faster but may miss nuanced details that would be caught in the incremental approach."
-- Request the user to select their preferred mode (e.g., "Please let me know if you'd prefer A or B.").
-- Once the user chooses, confirm the selected mode and proceed accordingly.
-
-### 2. Initialize Platform Validation
-
-- Review the infrastructure change documentation to understand platform implementation scope and purpose
-- Analyze the infrastructure architecture document for platform design patterns and compliance requirements
-- Examine infrastructure guidelines for organizational standards across all platform components
-- Prepare the validation environment and tools for comprehensive platform testing
-- <critical_rule>Verify the infrastructure change request is approved for validation. If not, HALT and inform the user.</critical_rule>
-
-### 3. Architecture Design Review Gate
-
-- **DevOps/Platform → Architect Design Review:**
-  - Conduct systematic review of infrastructure architecture document for implementability
-  - Evaluate architectural decisions against operational constraints and capabilities:
-    - **Implementation Complexity:** Assess if proposed architecture can be implemented with available tools and expertise
-    - **Operational Feasibility:** Validate that operational patterns are achievable within current organizational maturity
-    - **Resource Availability:** Confirm required infrastructure resources are available and within budget constraints
-    - **Technology Compatibility:** Verify selected technologies integrate properly with existing infrastructure
-    - **Security Implementation:** Validate that security patterns can be implemented with current security toolchain
-    - **Maintenance Overhead:** Assess ongoing operational burden and maintenance requirements
-  - Document design review findings and recommendations:
-    - **Approved Aspects:** Document architectural decisions that are implementable as designed
-    - **Implementation Concerns:** Identify architectural decisions that may face implementation challenges
-    - **Required Modifications:** Recommend specific changes needed to make architecture implementable
-    - **Alternative Approaches:** Suggest alternative implementation patterns where needed
-  - **Collaboration Decision Point:**
-    - If **critical implementation blockers** identified: HALT validation and escalate to Architect Agent for architectural revision
-    - If **minor concerns** identified: Document concerns and proceed with validation, noting required implementation adjustments
-    - If **architecture approved**: Proceed with comprehensive platform validation
-  - <critical_rule>All critical design review issues must be resolved before proceeding to detailed validation</critical_rule>
-
-### 4. Execute Comprehensive Platform Validation Process
-
-- **If "Incremental Mode" was selected:**
-
-  - For each section of the infrastructure checklist (Sections 1-16):
-    - **a. Present Section Purpose:** Explain what this section validates and why it's important for platform operations
-    - **b. Work Through Items:** Present each checklist item, guide the user through validation, and document compliance or gaps
-    - **c. Evidence Collection:** For each compliant item, document how compliance was verified
-    - **d. Gap Documentation:** For each non-compliant item, document specific issues and proposed remediation
-    - **e. Platform Integration Testing:** For platform engineering sections (13-16), validate integration between platform components
-    - **f. [Offer Advanced Self-Refinement & Elicitation Options](#offer-advanced-self-refinement--elicitation-options)**
-    - **g. Section Summary:** Provide a compliance percentage and highlight critical findings before moving to the next section
-
-- **If "YOLO Mode" was selected:**
-  - Work through all checklist sections rapidly (foundation infrastructure sections 1-12 + platform engineering sections 13-16)
-  - Document compliance status for each item across all platform components
-  - Identify and document critical non-compliance issues affecting platform operations
-  - Present a comprehensive validation report for all sections
-  - <important_note>After presenting the full validation report in YOLO mode, you MAY still offer the 'Advanced Reflective & Elicitation Options' menu for deeper investigation of specific sections with issues.</important_note>
-
-### 5. Generate Comprehensive Platform Validation Report
-
-- Summarize validation findings by section across all 16 checklist areas
-- Calculate and present overall compliance percentage for complete platform stack
-- Clearly document all non-compliant items with remediation plans prioritized by platform impact
-- Highlight critical security or operational risks affecting platform reliability
-- Include design review findings and architectural implementation recommendations
-- Provide validation signoff recommendation based on complete platform assessment
-- Document platform component integration validation results
-
-### 6. BMad Integration Assessment
-
-- Review how platform infrastructure changes support other BMad agents:
-  - **Development Agent Alignment:** Verify platform infrastructure supports Frontend Dev, Backend Dev, and Full Stack Dev requirements including:
-    - Container platform development environment provisioning
-    - GitOps workflows for application deployment
-    - Service mesh integration for development testing
-    - Developer experience platform self-service capabilities
-  - **Product Alignment:** Ensure platform infrastructure implements PRD requirements from Product Owner including:
-    - Scalability and performance requirements through container platform
-    - Deployment automation through GitOps workflows
-    - Service reliability through service mesh implementation
-  - **Architecture Alignment:** Validate that platform implementation aligns with architecture decisions including:
-    - Technology selections implemented correctly across all platform components
-    - Security architecture implemented in container platform, service mesh, and GitOps
-    - Integration patterns properly implemented between platform components
-  - Document all integration points and potential impacts on other agents' workflows
-
-### 7. Next Steps Recommendation
-
-- If validation successful:
-  - Prepare platform deployment recommendation with component dependencies
-  - Outline monitoring requirements for complete platform stack
-  - Suggest knowledge transfer activities for platform operations
-  - Document platform readiness certification
-- If validation failed:
-  - Prioritize remediation actions by platform component and integration impact
-  - Recommend blockers vs. non-blockers for platform deployment
-  - Schedule follow-up validation with focus on failed platform components
-  - Document platform risks and mitigation strategies
-- If design review identified architectural issues:
-  - **Escalate to Architect Agent** for architectural revision and re-design
-  - Document specific architectural changes required for implementability
-  - Schedule follow-up design review after architectural modifications
-- Update documentation with validation results across all platform components
-- <important_note>Always ensure the Infrastructure Change Request status is updated to reflect the platform validation outcome.</important_note>
-
-## Output
-
-A comprehensive platform validation report documenting:
-
-1. **Architecture Design Review Results** - Implementability assessment and architectural recommendations
-2. **Compliance percentage by checklist section** (all 16 sections including platform engineering)
-3. **Detailed findings for each non-compliant item** across foundation and platform components
-4. **Platform integration validation results** documenting component interoperability
-5. **Remediation recommendations with priority levels** based on platform impact
-6. **BMad integration assessment results** for complete platform stack
-7. **Clear signoff recommendation** for platform deployment readiness or architectural revision requirements
-8. **Next steps for implementation or remediation** prioritized by platform dependencies
-
-## 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. **Critical Security Assessment & Risk Analysis**
-2. **Platform Integration & Component Compatibility Evaluation**
-3. **Cross-Environment Consistency Review**
-4. **Technical Debt & Maintainability Analysis**
-5. **Compliance & Regulatory Alignment Deep Dive**
-6. **Cost Optimization & Resource Efficiency Analysis**
-7. **Operational Resilience & Platform Failure Mode Testing (Theoretical)**
-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)