378 lines
18 KiB
Markdown
378 lines
18 KiB
Markdown
# BMAD Method Improvements
|
|
|
|
## MPC (Machine-Powered Capabilities) Integration
|
|
|
|
The BMAD Method now supports integration with external tools and services through a structured MPC framework:
|
|
|
|
### 1. MPC Configuration System
|
|
- **Centralized Configuration**: All available MPCs are defined in a central YAML file
|
|
- **Role-Based Access**: MPCs are assigned to specific agent roles
|
|
- **Use Case Documentation**: Each MPC includes documentation on ideal use cases
|
|
- **Command Interface**: Standardized commands for invoking external capabilities
|
|
|
|
### 2. Available MPCs
|
|
- **Search Tools**: Perplexity for web research and summarization
|
|
- **Code Search**: GitHub for finding implementation examples and documentation
|
|
- **Data Analysis**: Firecrawl for advanced data mining and pattern recognition
|
|
- **Image Generation**: DALL-E for UI mockups and concept visualization
|
|
|
|
### 3. Integration Features
|
|
- **Task-Specific Usage**: Agents suggest appropriate MPCs for specific tasks
|
|
- **Workflow Integration**: MPC usage is seamlessly integrated into agent workflows
|
|
- **Knowledge Base Updates**: MPC outputs can be incorporated into project knowledge
|
|
- **Command System**: Simple asterisk-prefixed commands (e.g., *perplexity, *github)
|
|
|
|
### 4. User Benefits
|
|
- **Enhanced Research**: Better information gathering during early project phases
|
|
- **Implementation Guidance**: Code examples and documentation for development
|
|
- **Visual Prototyping**: Rapid generation of visual concepts
|
|
- **Data-Driven Decisions**: Improved analysis capabilities for business insights
|
|
|
|
## New Knowledge Enrichment System
|
|
|
|
The BMAD Method now includes a powerful agent knowledge enrichment system that allows agents to accumulate and share project-specific knowledge throughout the development lifecycle:
|
|
|
|
### 1. Knowledge Update Task
|
|
- **Purpose**: Automatically extract project information and update agent knowledge
|
|
- **Implementation**:
|
|
- New task file (`agent-knowledge-update-task.md`)
|
|
- JavaScript implementation (`create-knowledge-files.js`)
|
|
- Knowledge file templates in the templates directory
|
|
- **Benefits**:
|
|
- Agents become more effective with project-specific context
|
|
- Reduces repetition of information across agent interactions
|
|
- Creates a consistent knowledge base for all agents
|
|
|
|
### 2. Knowledge File Structure
|
|
- `.ai/project-context.md` - General project information and terminology
|
|
- `.ai/tech-stack.md` - Technical stack and implementation details
|
|
- `.ai/data-models.md` - Data structures and analytics approach
|
|
- `.ai/deployment-info.md` - Infrastructure and deployment information
|
|
|
|
### 3. Agent Customization
|
|
- Developer agents receive tech stack-specific customization
|
|
- QA agents receive testing approach customization
|
|
- DevOps agents receive deployment and infrastructure customization
|
|
- Data Science agents receive data and model customization
|
|
|
|
### 4. Integration Points
|
|
- After Analyst creates Project Brief
|
|
- After PM creates PRD
|
|
- After Architect creates system architecture
|
|
- Can be triggered manually at any point with the *update-agents command
|
|
|
|
## Advanced Knowledge Management Features
|
|
|
|
The BMAD Method now includes sophisticated knowledge management capabilities:
|
|
|
|
### 1. Knowledge Visualization
|
|
- **Knowledge Map Generation**: Creates visual representations of project components and relationships
|
|
- **Mermaid Diagrams**: Automatically generated architecture, data flow, and team responsibility diagrams
|
|
- **Gap Identification**: Visually highlights areas where knowledge is incomplete
|
|
|
|
### 2. Knowledge Request System
|
|
- **Structured Process**: Formal system for agents to request missing information
|
|
- **Knowledge Request Log**: Central repository of all information requests
|
|
- **Prioritization**: Requests are categorized by impact and urgency
|
|
- **Resolution Tracking**: Complete lifecycle tracking from request to resolution
|
|
|
|
### 3. Knowledge Versioning
|
|
- **Version History**: Tracks all changes to the knowledge base over time
|
|
- **Impact Analysis**: Documents how knowledge changes affect different project aspects
|
|
- **Changelog**: Detailed records of what information was added, changed, or removed
|
|
- **Cross-Project Learning**: Enables review of how project understanding evolved
|
|
|
|
### 4. Knowledge Validation
|
|
- **Consistency Checking**: Ensures information is consistent across all knowledge files
|
|
- **Completeness Verification**: Identifies missing required information
|
|
- **External Validation**: Compares knowledge against authoritative project documents
|
|
- **Knowledge Health Reporting**: Provides a comprehensive assessment of knowledge quality
|
|
|
|
## New Specialized Personas
|
|
|
|
The BMAD Method has been enhanced with three new specialized personas to provide more comprehensive project coverage:
|
|
|
|
### 1. QA Tester (Quinn)
|
|
- **Focus**: Comprehensive testing, quality assurance, and defect prevention
|
|
- **Key Tasks**:
|
|
- Creating detailed test plans
|
|
- Performing test execution and validation
|
|
- Generating quality reports
|
|
- Running QA-specific checklists
|
|
- **Benefits**:
|
|
- Earlier detection of defects
|
|
- Improved product quality
|
|
- More thorough validation of requirements
|
|
- Better regression prevention
|
|
|
|
### 2. DevOps Engineer (Derek)
|
|
- **Focus**: Deployment automation, infrastructure management, and operational excellence
|
|
- **Key Tasks**:
|
|
- Creating deployment plans
|
|
- Implementing infrastructure as code
|
|
- Managing CI/CD pipelines
|
|
- Ensuring security and compliance
|
|
- **Benefits**:
|
|
- Streamlined deployment process
|
|
- Improved system reliability
|
|
- Better monitoring and observability
|
|
- Enhanced security posture
|
|
|
|
### 3. Data Scientist (Diana)
|
|
- **Focus**: Data analysis, machine learning, and actionable insights
|
|
- **Key Tasks**:
|
|
- Creating data analysis plans
|
|
- Developing ML models
|
|
- Designing data pipelines
|
|
- Generating business intelligence
|
|
- **Benefits**:
|
|
- Data-driven decision making
|
|
- Enhanced product capabilities through ML/AI
|
|
- Better understanding of user behavior
|
|
- Predictive analytics for business planning
|
|
|
|
## Workflow Integration
|
|
|
|
These new personas are fully integrated into both the web-based and IDE-based BMAD workflows:
|
|
|
|
1. **Configuration Updates**:
|
|
- Added to both web and IDE orchestrator configurations
|
|
- Configured with appropriate tasks and checklists
|
|
- Interaction modes (Interactive/YOLO) supported
|
|
|
|
2. **Task Creation**:
|
|
- Specialized tasks created for each new persona
|
|
- Tasks follow standard BMAD Method format
|
|
- Tasks integrate with existing project artifacts
|
|
|
|
3. **Checklist Integration**:
|
|
- Specialized checklists created for quality validation
|
|
- Checklist mappings updated for new document types
|
|
- Integrated with checklist runner task
|
|
|
|
## Recommended Usage
|
|
|
|
For optimal results with the enhanced BMAD Method:
|
|
|
|
1. **Development Phase Integration**:
|
|
- QA Tester should be engaged early in story development
|
|
- DevOps Engineer should be involved in architecture planning
|
|
- Data Scientist should participate in requirements gathering when data needs exist
|
|
|
|
2. **Workflow Optimization**:
|
|
- Use web agents for high-level planning and design
|
|
- Use IDE agents for implementation phases
|
|
- Consider dedicated instances for frequently used personas
|
|
|
|
3. **Configuration Customization**:
|
|
- Update persona specializations based on project tech stack
|
|
- Adjust task priorities based on project requirements
|
|
- Customize checklists to match organizational standards
|
|
|
|
The enhanced BMAD Method now provides more comprehensive coverage across the entire software development lifecycle, from planning through implementation, quality assurance, and deployment.
|
|
|
|
## System Standardization and Consistency Improvements
|
|
|
|
The BMAD Method has undergone comprehensive standardization to eliminate inconsistencies and improve reliability across all agents and workflows:
|
|
|
|
### 1. Date Generation Standardization
|
|
|
|
**Problem Addressed**: Agents were generating documents with incorrect placeholder dates or inconsistent date formats, leading to confusion and unprofessional documentation.
|
|
|
|
**Solution Implemented**:
|
|
- **Standardized Date Format**: All dates now use `YYYY-MM-DD` format (e.g., `2024-01-15`)
|
|
- **Timestamp Format**: Timestamps use `YYYY-MM-DD HH:MM` format (e.g., `2024-01-15 14:30`)
|
|
- **Eliminated Placeholders**: Removed all date placeholders like `{DATE}`, `[DATE]`, or `TBD`
|
|
- **Automatic Generation**: All agents now generate actual current dates when creating documents
|
|
|
|
**Implementation Details**:
|
|
- Updated `knowledge-version-tmpl.md` with clear date generation instructions
|
|
- Enhanced `agent-knowledge-update-task.md` with critical date handling reminders
|
|
- Modified `dev.ide.md` persona to use proper date format examples
|
|
- Verified `create-knowledge-files.js` correctly generates dates using JavaScript Date API
|
|
|
|
### 2. File Naming Convention Standardization
|
|
|
|
**Problem Addressed**: Inconsistent file naming patterns across projects made it difficult to locate and reference documents, with variations like `PROJECT-BRIEF.MD`, `{project-name}-project-brief.md`, and `project-brief.md`.
|
|
|
|
**Solution Implemented**:
|
|
- **Consistent Lowercase with Hyphens**: All core BMAD documents now use lowercase filenames with hyphens
|
|
- **Standardized Core Documents**: Established canonical names for all major document types
|
|
- **Agent Training**: Updated all agents to recognize and suggest standard naming conventions
|
|
|
|
**Standard Naming Convention**:
|
|
|
|
| Document Type | Standard Filename | Agent Responsible |
|
|
|---------------|-------------------|-------------------|
|
|
| Project Brief | `project-brief.md` | Analyst |
|
|
| Product Requirements | `prd.md` | PM |
|
|
| Architecture | `architecture.md` | Architect |
|
|
| Frontend Architecture | `frontend-architecture.md` | Design Architect |
|
|
| UX/UI Specification | `uxui-spec.md` | Design Architect |
|
|
| Technology Stack | `tech-stack.md` | Architect |
|
|
| Data Models | `data-models.md` | Architect/Data Scientist |
|
|
| API Reference | `api-reference.md` | Architect |
|
|
| Deployment Guide | `deployment-guide.md` | DevOps |
|
|
| Test Plan | `test-plan.md` | QA |
|
|
| User Stories | `{epic-num}.{story-num}.story.md` | SM |
|
|
| Epic Files | `epic-{id}.md` | SM (from sharding) |
|
|
|
|
### 3. Files Modified
|
|
|
|
**Core Documentation**:
|
|
- `bmad-agent/commands.md` - Added comprehensive file organization guidelines and naming standards table
|
|
|
|
**Templates Updated**:
|
|
- `bmad-agent/templates/knowledge-version-tmpl.md` - Added date generation instructions and examples
|
|
- `bmad-agent/templates/doc-sharding-tmpl.md` - Updated to reference standard naming conventions
|
|
- `bmad-agent/templates/story-tmpl.md` - Updated template to use hyphenated naming format
|
|
|
|
**Task Files Updated**:
|
|
- `bmad-agent/tasks/agent-knowledge-update-task.md` - Added critical date handling reminders and standard filename references
|
|
- `bmad-agent/tasks/create-next-story-task.md` - Fixed story filename format to use hyphens
|
|
- `bmad-agent/tasks/create-knowledge-files.js` - Added references to standard naming conventions
|
|
|
|
**Persona Files Updated**:
|
|
- `bmad-agent/personas/dev.ide.md` - Updated story file reference and date format examples
|
|
|
|
### 4. Implementation Details
|
|
|
|
**Backward Compatibility**:
|
|
- System continues to work with existing non-standard filenames
|
|
- Agents suggest migration to standard naming when encountering non-standard files
|
|
- No breaking changes to existing workflows
|
|
|
|
**Automatic Enforcement**:
|
|
- All new documents automatically follow standard naming conventions
|
|
- Knowledge update process references correct standard filenames
|
|
- Document sharding process suggests standard naming for source files
|
|
|
|
**Agent Behavior**:
|
|
- Agents now validate and suggest correct filenames during document creation
|
|
- Cross-references between documents use standard naming
|
|
- Error messages and guidance reference standard conventions
|
|
|
|
### 5. Benefits
|
|
|
|
**Improved Consistency**:
|
|
- Predictable file locations across all BMAD Method projects
|
|
- Consistent cross-references between agents and documents
|
|
- Standardized date formats eliminate confusion and improve professionalism
|
|
|
|
**Enhanced Usability**:
|
|
- Easier file discovery and organization
|
|
- Reduced cognitive load when working across multiple projects
|
|
- Improved automation and scripting capabilities
|
|
|
|
**Better Maintainability**:
|
|
- Simplified documentation management
|
|
- Easier integration with external tools and systems
|
|
- Reduced errors from filename variations
|
|
|
|
**Professional Quality**:
|
|
- All generated documents now have proper dates
|
|
- Consistent naming creates a more professional appearance
|
|
- Improved reliability for client-facing deliverables
|
|
|
|
**Developer Experience**:
|
|
- Faster onboarding to new projects using BMAD Method
|
|
- Reduced time spent searching for specific documents
|
|
- More reliable automation and tooling integration
|
|
|
|
### 6. Migration Guidance
|
|
|
|
**For Existing Projects**:
|
|
1. Run `*BMAD Update Agent Knowledge` to apply new standards
|
|
2. Consider renaming existing files to match standard conventions
|
|
3. Update any custom scripts or tools to use new naming patterns
|
|
|
|
**For New Projects**:
|
|
- All documents will automatically follow standard naming
|
|
- Dates will be properly generated in all new documents
|
|
- Cross-references will use consistent naming patterns
|
|
|
|
This standardization effort significantly improves the reliability, consistency, and professional quality of the BMAD Method across all use cases and project types.
|
|
|
|
## Platform Engineer Role Addition
|
|
|
|
### Enhancement Overview
|
|
Added a comprehensive Platform Engineer role to complement the existing DevOps Engineer, providing specialized capabilities for complex infrastructure and developer experience optimization.
|
|
|
|
### New Capabilities Added
|
|
**Platform Engineer (Alex)** - Expert in developer experience, internal tooling, and platform services:
|
|
|
|
**Core Expertise Areas:**
|
|
- **Developer Experience Platforms** (90%+ confidence) - Self-service infrastructure, developer portals, golden path templates
|
|
- **Container Orchestration & Management** (90%+ confidence) - Advanced Kubernetes operations, workload optimization
|
|
- **Infrastructure as Code & Automation** (90%+ confidence) - Declarative infrastructure, state management, configuration drift detection
|
|
- **Service Mesh & Communication Operations** (90%+ confidence) - Service mesh implementation, traffic management, inter-service monitoring
|
|
- **Platform Operations** (90%+ confidence) - Secrets management, CI/CD platform architecture, incident response
|
|
- **Advanced Platform Engineering** (70-90% confidence) - Observability systems, security toolchain integration, chaos engineering
|
|
- **Emerging Specializations** (50-70% confidence) - Regulatory compliance, FinOps, environmental sustainability
|
|
|
|
### Implementation Details
|
|
**Files Created:**
|
|
- `bmad-agent/personas/platform-engineer.md` - Complete Platform Engineer persona following BMAD naming standards
|
|
- `bmad-agent/tasks/platform-change-management.md` - Comprehensive platform change management task
|
|
|
|
**Files Updated:**
|
|
- `bmad-agent/ide-bmad-orchestrator.cfg.md` - Added Platform Engineer configuration
|
|
- `bmad-agent/commands.md` - Updated standard naming convention table with platform documents
|
|
|
|
### Role Differentiation
|
|
**DevOps Engineer (Derek)**: Focuses on application deployment, basic infrastructure, and operational tasks
|
|
**Platform Engineer (Alex)**: Specializes in developer experience, platform services, and complex infrastructure architecture
|
|
|
|
### Benefits
|
|
- **Enhanced Infrastructure Capabilities**: Advanced platform engineering for complex projects
|
|
- **Improved Developer Experience**: Specialized focus on developer productivity and self-service platforms
|
|
- **Complementary Roles**: DevOps handles operations while Platform Engineer builds the platform
|
|
- **Scalability**: Better support for enterprise-scale and multi-team environments
|
|
- **Standards Compliance**: Follows all BMAD naming conventions and date generation standards
|
|
|
|
### Usage Guidance
|
|
- **Use DevOps Engineer** for: Basic deployment, monitoring, CI/CD setup, operational tasks
|
|
- **Use Platform Engineer** for: Developer platforms, complex infrastructure, service mesh, advanced automation, internal tooling
|
|
|
|
This addition provides the BMAD Method with robust infrastructure capabilities while maintaining the existing operational excellence of the DevOps Engineer role.
|
|
|
|
### Command Reference Integration
|
|
|
|
**Comprehensive Documentation Updates:**
|
|
Following the Platform Engineer addition, the BMAD Method Command Reference Guide was updated to fully integrate the new role across all workflows and scenarios.
|
|
|
|
**Files Updated:**
|
|
- `bmad-agent/commands.md` - Enhanced with Platform Engineer integration across all relevant scenarios
|
|
|
|
**Workflow Enhancements:**
|
|
|
|
**1. Enhanced Common Scenarios:**
|
|
- **Complete Project Initialization Flow**: Added Platform Engineer as step 4 for complex projects with clear guidance on when to include/skip
|
|
- **Adding New Module to Existing Project**: Added Platform Engineer for complex module infrastructure with role separation guidance
|
|
- **New Platform Infrastructure Setup Scenario**: Complete workflow for establishing comprehensive platform infrastructure
|
|
|
|
**2. Decision Framework Added:**
|
|
Clear criteria for infrastructure role selection:
|
|
|
|
| Use DevOps Engineer | Use Platform Engineer |
|
|
|-------------------|---------------------|
|
|
| Basic deployment & CI/CD | Complex infrastructure (microservices, service mesh) |
|
|
| Standard monitoring | Developer experience platforms |
|
|
| Simple infrastructure | Multi-team environments |
|
|
| Single-team projects | Advanced observability & monitoring |
|
|
| | Internal tooling & self-service platforms |
|
|
|
|
**3. Enhanced Best Practices:**
|
|
- **Standard Projects Flow**: Traditional workflow without Platform Engineer
|
|
- **Complex Projects Flow**: Enhanced workflow including Platform Engineer
|
|
- **Infrastructure Role Selection Guide**: Clear decision criteria and use cases
|
|
|
|
**Benefits:**
|
|
- **Clear Guidance**: Users know exactly when to use which infrastructure role
|
|
- **Comprehensive Coverage**: All scenarios account for both infrastructure roles
|
|
- **Scalability Support**: Handles both simple and complex project requirements
|
|
- **Decision Support**: Clear criteria eliminate confusion about role selection
|
|
- **Complete Integration**: Platform Engineer fully integrated into all relevant workflows
|
|
|
|
**Implementation Impact:**
|
|
The command reference now provides complete guidance for leveraging both infrastructure roles effectively, ensuring users can make informed decisions about which agent to use based on their project complexity and requirements. This creates a seamless experience whether working on simple applications or complex enterprise platforms. |