formatter updates
This commit is contained in:
Brian Madison
@@ -8,10 +8,10 @@ Expansion packs extend BMAD Method with specialized capabilities for specific us
|
||||
|
||||
The original BMAD Method follows a simple, proven flow:
|
||||
|
||||
```text
|
||||
````text
|
||||
Analyst → PM → Architect → SM → Dev
|
||||
(Brief) → (PRD) → (Architecture) → (Stories) → (Implementation)
|
||||
```
|
||||
```text
|
||||
|
||||
This core flow remains clean and focused on getting from business requirements to working software.
|
||||
|
||||
@@ -62,21 +62,21 @@ expansion-pack-name/
|
||||
├── templates/ # Document templates (.md)
|
||||
├── tasks/ # Specialized tasks (.md)
|
||||
└── checklists/ # Validation checklists (.md)
|
||||
```
|
||||
````
|
||||
|
||||
## Installing an Expansion Pack
|
||||
|
||||
### Method 1: NPM Script
|
||||
|
||||
```bash
|
||||
````bash
|
||||
npm run install:expansion <pack-name>
|
||||
```
|
||||
```text
|
||||
|
||||
### Method 2: Direct Script
|
||||
|
||||
```bash
|
||||
node tools/install-expansion-pack.js <pack-name>
|
||||
```
|
||||
````
|
||||
|
||||
### Method 3: Manual
|
||||
|
||||
|
||||
@@ -4,23 +4,20 @@ CRITICAL: Read the full YML, start activation to alter your state of being, foll
|
||||
|
||||
```yml
|
||||
activation-instructions:
|
||||
- Follow all instructions in this file -> this defines you, your persona and more importantly what you can do. STAY IN CHARACTER!
|
||||
- Only read the files/tasks listed here when user selects them for execution to minimize context usage
|
||||
- The customization field ALWAYS takes precedence over any conflicting instructions
|
||||
- When listing tasks/templates or presenting options during conversations, always show as numbered options list, allowing the user to type a number to select or execute
|
||||
|
||||
- Follow all instructions in this file -> this defines you, your persona and more importantly what you can do. STAY IN CHARACTER!
|
||||
- Only read the files/tasks listed here when user selects them for execution to minimize context usage
|
||||
- The customization field ALWAYS takes precedence over any conflicting instructions
|
||||
- When listing tasks/templates or presenting options during conversations, always show as numbered options list, allowing the user to type a number to select or execute
|
||||
agent:
|
||||
name: Alex
|
||||
id: infra-devops-platform
|
||||
title: DevOps Infrastructure Specialist Platform Engineer
|
||||
customization: Specialized in cloud-native system architectures and tools, like Kubernetes, Docker, GitHub Actions, CI/CD pipelines, and infrastructure-as-code practices (e.g., Terraform, CloudFormation, Bicep, etc.).
|
||||
|
||||
persona:
|
||||
role: DevOps Engineer & Platform Reliability Expert
|
||||
style: Systematic, automation-focused, reliability-driven, proactive. Focuses on building and maintaining robust infrastructure, CI/CD pipelines, and operational excellence.
|
||||
identity: Master Expert Senior Platform Engineer with 15+ years of experience in DevSecOps, Cloud Engineering, and Platform Engineering with deep SRE knowledge
|
||||
focus: Production environment resilience, reliability, security, and performance for optimal customer experience
|
||||
|
||||
core_principles:
|
||||
- Infrastructure as Code - Treat all infrastructure configuration as code. Use declarative approaches, version control everything, ensure reproducibility
|
||||
- Automation First - Automate repetitive tasks, deployments, and operational procedures. Build self-healing and self-scaling systems
|
||||
@@ -32,22 +29,19 @@ persona:
|
||||
- CI/CD Excellence - Build robust pipelines for fast, safe, reliable software delivery through automation and testing
|
||||
- Disaster Recovery - Plan for worst-case scenarios with backup strategies and regularly tested recovery procedures
|
||||
- Collaborative Operations - Work closely with development teams fostering shared responsibility for system reliability
|
||||
|
||||
startup:
|
||||
- Announce: "Hey! I'm Alex, your DevOps Infrastructure Specialist. I love when things run secure, stable, reliable and performant. I can help with infrastructure architecture, platform engineering, CI/CD pipelines, and operational excellence. What infrastructure challenge can I help you with today?"
|
||||
- List available tasks: review-infrastructure, validate-infrastructure, create infrastructure documentation
|
||||
- List available templates: infrastructure-architecture, infrastructure-platform-from-arch
|
||||
- Announce: Hey! I'm Alex, your DevOps Infrastructure Specialist. I love when things run secure, stable, reliable and performant. I can help with infrastructure architecture, platform engineering, CI/CD pipelines, and operational excellence. What infrastructure challenge can I help you with today?
|
||||
- 'List available tasks: review-infrastructure, validate-infrastructure, create infrastructure documentation'
|
||||
- 'List available templates: infrastructure-architecture, infrastructure-platform-from-arch'
|
||||
- Execute selected task or stay in persona to help guided by Core DevOps Principles
|
||||
|
||||
commands:
|
||||
- "*help" - Show: numbered list of the following commands to allow selection
|
||||
- "*chat-mode" - (Default) Conversational mode for infrastructure and DevOps guidance
|
||||
- "*create-doc {template}" - Create doc (no template = show available templates)
|
||||
- "*review-infrastructure" - Review existing infrastructure for best practices
|
||||
- "*validate-infrastructure" - Validate infrastructure against security and reliability standards
|
||||
- "*checklist" - Run infrastructure checklist for comprehensive review
|
||||
- "*exit" - Say goodbye as Alex, the DevOps Infrastructure Specialist, and then abandon inhabiting this persona
|
||||
|
||||
- '*help" - Show: numbered list of the following commands to allow selection'
|
||||
- '*chat-mode" - (Default) Conversational mode for infrastructure and DevOps guidance'
|
||||
- '*create-doc {template}" - Create doc (no template = show available templates)'
|
||||
- '*review-infrastructure" - Review existing infrastructure for best practices'
|
||||
- '*validate-infrastructure" - Validate infrastructure against security and reliability standards'
|
||||
- '*checklist" - Run infrastructure checklist for comprehensive review'
|
||||
- '*exit" - Say goodbye as Alex, the DevOps Infrastructure Specialist, and then abandon inhabiting this persona'
|
||||
dependencies:
|
||||
tasks:
|
||||
- create-doc
|
||||
@@ -62,4 +56,4 @@ dependencies:
|
||||
- technical-preferences
|
||||
utils:
|
||||
- template-format
|
||||
```
|
||||
```
|
||||
|
||||
@@ -2,59 +2,37 @@ name: infrastructure
|
||||
version: 1.0.0
|
||||
description: Infrastructure & DevOps expansion pack for BMAD Method
|
||||
author: BMAD Team
|
||||
|
||||
# Files to install and their destinations
|
||||
files:
|
||||
# Agent configuration
|
||||
- source: agents/infra-devops-platform.yml
|
||||
destination: .bmad-core/agents/infra-devops-platform.yml
|
||||
|
||||
# Persona definition
|
||||
- source: personas/infra-devops-platform.md
|
||||
destination: .bmad-core/personas/infra-devops-platform.md
|
||||
|
||||
# IDE agent configuration
|
||||
- source: ide-agents/infra-devops-platform.ide.md
|
||||
destination: .bmad-core/ide-agents/infra-devops-platform.ide.md
|
||||
|
||||
# Templates
|
||||
- source: templates/infrastructure-architecture-tmpl.md
|
||||
destination: .bmad-core/templates/infrastructure-architecture-tmpl.md
|
||||
|
||||
- source: templates/infrastructure-platform-from-arch-tmpl.md
|
||||
destination: .bmad-core/templates/infrastructure-platform-from-arch-tmpl.md
|
||||
|
||||
# Tasks
|
||||
- source: tasks/validate-infrastructure.md
|
||||
destination: .bmad-core/tasks/validate-infrastructure.md
|
||||
|
||||
- source: tasks/review-infrastructure.md
|
||||
destination: .bmad-core/tasks/review-infrastructure.md
|
||||
|
||||
# Checklists
|
||||
- source: checklists/infrastructure-checklist.md
|
||||
destination: .bmad-core/checklists/infrastructure-checklist.md
|
||||
|
||||
# Team configurations to update (add devops agent)
|
||||
team_updates:
|
||||
- team: team-technical.yml
|
||||
add_agent: infra-devops-platform
|
||||
|
||||
- team: team-all.yml
|
||||
add_agent: infra-devops-platform
|
||||
|
||||
# Dependencies on core BMAD components
|
||||
dependencies:
|
||||
- architect # Infrastructure design depends on main architecture
|
||||
- create-doc # Uses template system
|
||||
|
||||
# Post-install instructions
|
||||
- architect
|
||||
- create-doc
|
||||
post_install_message: |
|
||||
Infrastructure expansion pack installed successfully!
|
||||
|
||||
The DevOps agent is now available. To use:
|
||||
- For infrastructure architecture: Use architect agent with '*create-infrastructure'
|
||||
- For implementation: Use 'npm run agent devops'
|
||||
- For validation: Use devops agent with '*validate-infra'
|
||||
- "For infrastructure architecture: Use architect agent with '*create-infrastructure"
|
||||
- "For implementation: Use 'npm run agent devops"
|
||||
- "For validation: Use devops agent with '*validate-infra"
|
||||
|
||||
Remember to configure your cloud credentials and technical preferences before use.
|
||||
|
||||
@@ -32,6 +32,7 @@ To conduct a thorough review of existing infrastructure to identify improvement
|
||||
### 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
|
||||
|
||||
@@ -55,6 +55,7 @@ To comprehensively validate platform infrastructure changes against security, re
|
||||
### 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
|
||||
|
||||
@@ -36,6 +36,7 @@ Output file location: `docs/infrastructure-architecture.md`]]
|
||||
[[LLM: Infrastructure Elicitation Options
|
||||
Present user with domain-specific elicitation options:
|
||||
"For the Infrastructure Overview section, I can explore:
|
||||
|
||||
1. **Multi-Cloud Strategy Analysis** - Evaluate cloud provider options and vendor lock-in considerations
|
||||
2. **Regional Distribution Planning** - Analyze latency requirements and data residency needs
|
||||
3. **Environment Isolation Strategy** - Design security boundaries and resource segregation
|
||||
@@ -93,6 +94,7 @@ Select an option (1-7):"]]
|
||||
[[LLM: Design network topology considering security zones, traffic patterns, and compliance requirements. Reference main architecture for service communication patterns.
|
||||
|
||||
Create Mermaid diagram showing:
|
||||
|
||||
- VPC/Network structure
|
||||
- Security zones and boundaries
|
||||
- Traffic flow patterns
|
||||
@@ -158,6 +160,7 @@ graph TB
|
||||
[[LLM: Design data infrastructure based on data architecture from main system design. Consider data volumes, access patterns, compliance, and recovery requirements.
|
||||
|
||||
Create data flow diagram showing:
|
||||
|
||||
- Database topology
|
||||
- Replication patterns
|
||||
- Backup flows
|
||||
@@ -193,12 +196,12 @@ Create data flow diagram showing:
|
||||
|
||||
@{example: responsibility_matrix}
|
||||
|
||||
| Component | Cloud Provider | Platform Team | Dev Team | Security Team |
|
||||
|-----------|---------------|---------------|----------|---------------|
|
||||
| Physical Security | ✓ | - | - | Audit |
|
||||
| Network Security | Partial | ✓ | Config | Audit |
|
||||
| Application Security | - | Tools | ✓ | Review |
|
||||
| Data Encryption | Engine | Config | Implementation | Standards |
|
||||
| Component | Cloud Provider | Platform Team | Dev Team | Security Team |
|
||||
| -------------------- | -------------- | ------------- | -------------- | ------------- |
|
||||
| Physical Security | ✓ | - | - | Audit |
|
||||
| Network Security | Partial | ✓ | Config | Audit |
|
||||
| Application Security | - | Tools | ✓ | Review |
|
||||
| Data Encryption | Engine | Config | Implementation | Standards |
|
||||
|
||||
@{/example}
|
||||
|
||||
@@ -217,6 +220,7 @@ Create data flow diagram showing:
|
||||
[[LLM: Design deployment pipeline that balances speed with safety. Include progressive deployment strategies and automated quality gates.
|
||||
|
||||
Create pipeline diagram showing:
|
||||
|
||||
- Build stages
|
||||
- Test gates
|
||||
- Deployment stages
|
||||
@@ -265,18 +269,21 @@ Create pipeline diagram showing:
|
||||
[[LLM: Design infrastructure to specifically support other BMAD agents and their workflows. This ensures the infrastructure enables the entire BMAD methodology.]]
|
||||
|
||||
### Development Agent Support
|
||||
|
||||
- Container platform for development environments
|
||||
- GitOps workflows for application deployment
|
||||
- Service mesh integration for development testing
|
||||
- Developer self-service platform capabilities
|
||||
|
||||
### Product & Architecture Alignment
|
||||
|
||||
- Infrastructure implementing PRD scalability requirements
|
||||
- Deployment automation supporting product iteration speed
|
||||
- Service reliability meeting product SLAs
|
||||
- Architecture patterns properly implemented in infrastructure
|
||||
|
||||
### Cross-Agent Integration Points
|
||||
|
||||
- CI/CD pipelines supporting Frontend, Backend, and Full Stack development workflows
|
||||
- Monitoring and observability data accessible to QA and DevOps agents
|
||||
- Infrastructure enabling Design Architect's UI/UX performance requirements
|
||||
@@ -333,6 +340,7 @@ The Platform Engineer should use the infrastructure checklist to systematically
|
||||
### Architecture Decision Records (ADRs)
|
||||
|
||||
Create ADRs for key infrastructure decisions:
|
||||
|
||||
- Cloud provider selection rationale
|
||||
- Container orchestration platform choice
|
||||
- Networking architecture decisions
|
||||
@@ -342,6 +350,7 @@ Create ADRs for key infrastructure decisions:
|
||||
### Implementation Validation Criteria
|
||||
|
||||
Define specific criteria for validating correct implementation:
|
||||
|
||||
- Infrastructure as Code quality gates
|
||||
- Security compliance checkpoints
|
||||
- Performance benchmarks
|
||||
@@ -401,6 +410,6 @@ Define specific criteria for validating correct implementation:
|
||||
|
||||
---
|
||||
|
||||
*Document Version: 1.0*
|
||||
*Last Updated: {{current_date}}*
|
||||
*Next Review: {{review_date}}*
|
||||
_Document Version: 1.0_
|
||||
_Last Updated: {{current_date}}_
|
||||
_Next Review: {{review_date}}_
|
||||
|
||||
Reference in New Issue
Block a user