doc and text cleanup
This commit is contained in:
Brian Madison
@@ -1,3 +1,3 @@
|
||||
# BMAD Method Expansion Packs
|
||||
# BMad Method Expansion Packs
|
||||
|
||||
Expansion packs extend BMAD-METHOD beyond traditional software development, providing specialized agent teams, templates, and workflows for specific domains and industries. Each pack is a self-contained ecosystem designed to bring the power of AI-assisted workflows to any field. Coming soon.
|
||||
Expansion packs extend BMad-Method beyond traditional software development, providing specialized agent teams, templates, and workflows for specific domains and industries. Each pack is a self-contained ecosystem designed to bring the power of AI-assisted workflows to any field. Coming soon.
|
||||
|
||||
@@ -2,6 +2,6 @@ name: bmad-2d-phaser-game-dev
|
||||
version: 1.3.0
|
||||
short-title: 2D game development with Phaser 3 & TypeScript
|
||||
description: >-
|
||||
2D Game Development expansion pack for BMAD Method - Phaser 3 & TypeScript
|
||||
2D Game Development expansion pack for BMad Method - Phaser 3 & TypeScript
|
||||
focused
|
||||
author: Brian (BMad)
|
||||
|
||||
@@ -1,8 +1,8 @@
|
||||
# Game Development BMAD Knowledge Base
|
||||
# Game Development BMad Knowledge Base
|
||||
|
||||
## Overview
|
||||
|
||||
This game development expansion of BMAD-METHOD specializes in creating 2D games using Phaser 3 and TypeScript. It extends the core BMAD framework with game-specific agents, workflows, and best practices for professional game development.
|
||||
This game development expansion of BMad-Method specializes in creating 2D games using Phaser 3 and TypeScript. It extends the core BMad framework with game-specific agents, workflows, and best practices for professional game development.
|
||||
|
||||
### Game Development Focus
|
||||
|
||||
@@ -251,4 +251,4 @@ game-project/
|
||||
- Culling and level-of-detail systems
|
||||
- Memory management and garbage collection optimization
|
||||
|
||||
This knowledge base provides the foundation for effective game development using the BMAD-METHOD framework with specialized focus on 2D game creation using Phaser 3 and TypeScript.
|
||||
This knowledge base provides the foundation for effective game development using the BMad-Method framework with specialized focus on 2D game creation using Phaser 3 and TypeScript.
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
# BMAD Creator Tools
|
||||
# BMad Creator Tools
|
||||
|
||||
Tools for creating and extending BMAD framework components.
|
||||
Tools for creating and extending BMad framework components.
|
||||
|
||||
## Tasks
|
||||
|
||||
|
||||
@@ -11,27 +11,27 @@ activation-instructions:
|
||||
agent:
|
||||
name: The Creator
|
||||
id: bmad-the-creator
|
||||
title: BMAD Framework Extension Specialist
|
||||
title: BMad Framework Extension Specialist
|
||||
icon: 🏗️
|
||||
whenToUse: Use for creating new agents, expansion packs, and extending the BMAD framework
|
||||
whenToUse: Use for creating new agents, expansion packs, and extending the BMad framework
|
||||
customization: null
|
||||
persona:
|
||||
role: Expert BMAD Framework Architect & Creator
|
||||
role: Expert BMad Framework Architect & Creator
|
||||
style: Methodical, creative, framework-aware, systematic
|
||||
identity: Master builder who extends BMAD capabilities through thoughtful design and deep framework understanding
|
||||
focus: Creating well-structured agents, expansion packs, and framework extensions that follow BMAD patterns and conventions
|
||||
identity: Master builder who extends BMad capabilities through thoughtful design and deep framework understanding
|
||||
focus: Creating well-structured agents, expansion packs, and framework extensions that follow BMad patterns and conventions
|
||||
core_principles:
|
||||
- Framework Consistency - All creations follow established BMAD patterns
|
||||
- Framework Consistency - All creations follow established BMad patterns
|
||||
- Modular Design - Create reusable, composable components
|
||||
- Clear Documentation - Every creation includes proper documentation
|
||||
- Convention Over Configuration - Follow BMAD naming and structure patterns
|
||||
- Convention Over Configuration - Follow BMad naming and structure patterns
|
||||
- Extensibility First - Design for future expansion and customization
|
||||
- Numbered Options Protocol - Always use numbered lists for user selections
|
||||
startup:
|
||||
- Greet the user with your name and role, and inform of the *help command
|
||||
- CRITICAL: Do NOT automatically create documents or execute tasks during startup
|
||||
- CRITICAL: Do NOT create or modify any files during startup
|
||||
- Offer to help with BMAD framework extensions but wait for explicit user confirmation
|
||||
- Offer to help with BMad framework extensions but wait for explicit user confirmation
|
||||
- Only execute tasks when user explicitly requests them
|
||||
commands:
|
||||
- '*help" - Show numbered list of available commands for selection'
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
name: bmad-creator-tools
|
||||
version: 1.2.0
|
||||
short-title: Tools for creating BMAD framework components
|
||||
description: Tools for creating and extending BMAD framework components.
|
||||
short-title: Tools for creating BMad framework components
|
||||
description: Tools for creating and extending BMad framework components.
|
||||
author: Brian (BMad)
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
# Create Agent Task
|
||||
|
||||
This task guides you through creating a new BMAD agent following the standard template.
|
||||
This task guides you through creating a new BMad agent following the standard template.
|
||||
|
||||
## Prerequisites
|
||||
|
||||
|
||||
@@ -1,10 +1,10 @@
|
||||
# Create Expansion Pack Task
|
||||
|
||||
This task helps you create a sophisticated BMAD expansion pack with advanced agent orchestration, template systems, and quality assurance patterns based on proven best practices.
|
||||
This task helps you create a sophisticated BMad expansion pack with advanced agent orchestration, template systems, and quality assurance patterns based on proven best practices.
|
||||
|
||||
## Understanding Expansion Packs
|
||||
|
||||
Expansion packs extend BMAD with domain-specific capabilities using sophisticated AI agent orchestration patterns. They are self-contained packages that leverage:
|
||||
Expansion packs extend BMad with domain-specific capabilities using sophisticated AI agent orchestration patterns. They are self-contained packages that leverage:
|
||||
|
||||
- **Advanced Agent Architecture**: YAML-in-Markdown with embedded personas and character consistency
|
||||
- **Template Systems**: LLM instruction embedding with conditional content and dynamic variables
|
||||
@@ -12,7 +12,7 @@ Expansion packs extend BMAD with domain-specific capabilities using sophisticate
|
||||
- **Quality Assurance**: Multi-level validation with star ratings and comprehensive checklists
|
||||
- **Knowledge Integration**: Domain-specific data organization and best practices embedding
|
||||
|
||||
Every expansion pack MUST include a custom BMAD orchestrator agent with sophisticated command systems and numbered options protocols.
|
||||
Every expansion pack MUST include a custom BMad orchestrator agent with sophisticated command systems and numbered options protocols.
|
||||
|
||||
## CRITICAL REQUIREMENTS
|
||||
|
||||
@@ -83,7 +83,7 @@ Create `expansion-packs/{pack-name}/plan.md` with:
|
||||
|
||||
### Agents (with Character Personas)
|
||||
|
||||
- [ ] {pack-name}-orchestrator (REQUIRED: Custom BMAD orchestrator)
|
||||
- [ ] {pack-name}-orchestrator (REQUIRED: Custom BMad orchestrator)
|
||||
- Character Name: {human-name}
|
||||
- Communication Style: {style}
|
||||
- Key Commands: {command-list}
|
||||
@@ -157,7 +157,7 @@ Important: Wait for user approval before proceeding to Phase 2
|
||||
|
||||
#### 2.1 Create Orchestrator Agent with Domain-Themed Character
|
||||
|
||||
**FIRST PRIORITY**: Design the custom BMAD orchestrator with domain-appropriate theme:
|
||||
**FIRST PRIORITY**: Design the custom BMad orchestrator with domain-appropriate theme:
|
||||
|
||||
**Themed Character Design:**
|
||||
|
||||
@@ -183,7 +183,7 @@ Important: Wait for user approval before proceeding to Phase 2
|
||||
- **Activation Instructions**: Embedded YAML with behavior directives
|
||||
- **Startup Procedures**: Initialize without auto-execution
|
||||
- **Dependencies**: Clear references to tasks, templates, and data files
|
||||
- **Integration Points**: How it coordinates with core BMAD agents
|
||||
- **Integration Points**: How it coordinates with core BMad agents
|
||||
|
||||
#### 2.2 Design Specialist Agents with Character Personas
|
||||
|
||||
@@ -374,7 +374,7 @@ embedded_knowledge:
|
||||
- {domain}-terminology.md
|
||||
- {domain}-standards.md
|
||||
|
||||
# Dependencies on core BMAD components
|
||||
# Dependencies on core BMad components
|
||||
core_dependencies:
|
||||
agents:
|
||||
- architect # For system design
|
||||
@@ -863,7 +863,7 @@ Embedded knowledge (automatic):
|
||||
7. "Where in the workflow should users choose between different paths?"
|
||||
8. "How should the orchestrator hand off to specialist agents?"
|
||||
9. "What quality gates should be built into the workflow?"
|
||||
10. "How should it integrate with core BMAD agents?"
|
||||
10. "How should it integrate with core BMad agents?"
|
||||
|
||||
### Agent Planning
|
||||
|
||||
@@ -913,7 +913,7 @@ Embedded knowledge (automatic):
|
||||
**Quality and Validation:**
|
||||
|
||||
- **Plan First**: ALWAYS create and get approval for plan.md before implementing
|
||||
- **Orchestrator Required**: Every pack MUST have a custom BMAD orchestrator with sophisticated command system
|
||||
- **Orchestrator Required**: Every pack MUST have a custom BMad orchestrator with sophisticated command system
|
||||
- **Verify References**: ALL referenced tasks/templates MUST exist and be tested
|
||||
- **Multi-Level Validation**: Quality systems must provide basic, comprehensive, and expert-level assessment
|
||||
- **Domain Expertise**: Ensure accuracy in specialized fields with embedded best practices
|
||||
|
||||
@@ -70,7 +70,7 @@ Users must add these files to `bmad-core/data/`:
|
||||
|
||||
## Integration Points
|
||||
|
||||
- Depends on core agents: {list any core BMAD agents used}
|
||||
- Depends on core agents: {list any core BMad agents used}
|
||||
- Extends teams: {which teams to update}
|
||||
|
||||
## Success Criteria
|
||||
|
||||
@@ -2,11 +2,11 @@
|
||||
|
||||
## Overview
|
||||
|
||||
This expansion pack extends BMAD Method with comprehensive infrastructure and DevOps capabilities. It's designed for teams that need to define, implement, and manage cloud infrastructure alongside their application development.
|
||||
This expansion pack extends BMad Method with comprehensive infrastructure and DevOps capabilities. It's designed for teams that need to define, implement, and manage cloud infrastructure alongside their application development.
|
||||
|
||||
## Purpose
|
||||
|
||||
While the core BMAD flow focuses on getting from business requirements to development (Analyst → PM → Architect → SM → Dev), many projects require sophisticated infrastructure planning and implementation. This expansion pack adds:
|
||||
While the core BMad flow focuses on getting from business requirements to development (Analyst → PM → Architect → SM → Dev), many projects require sophisticated infrastructure planning and implementation. This expansion pack adds:
|
||||
|
||||
- Infrastructure architecture design capabilities
|
||||
- Platform engineering implementation workflows
|
||||
@@ -52,9 +52,9 @@ Install this expansion pack when your project requires:
|
||||
|
||||
- `infrastructure-checklist.md` - Comprehensive 16-section infrastructure validation checklist
|
||||
|
||||
## Integration with Core BMAD
|
||||
## Integration with Core BMad
|
||||
|
||||
This expansion pack integrates with the core BMAD flow at these points:
|
||||
This expansion pack integrates with the core BMad flow at these points:
|
||||
|
||||
1. **After Architecture Phase**: The Architect can trigger infrastructure architecture design
|
||||
2. **Parallel to Development**: Infrastructure implementation can proceed alongside application development
|
||||
@@ -123,7 +123,7 @@ The DevOps agent can be added to team configurations:
|
||||
|
||||
This expansion pack works best when used with:
|
||||
|
||||
- Core BMAD agents (especially Architect)
|
||||
- Core BMad agents (especially Architect)
|
||||
- Technical preferences documentation
|
||||
- Approved PRD and system architecture
|
||||
|
||||
@@ -144,4 +144,4 @@ You can customize this expansion pack by:
|
||||
---
|
||||
|
||||
_Version: 1.0_
|
||||
_Compatible with: BMAD Method v4_
|
||||
_Compatible with: BMad Method v4_
|
||||
|
||||
@@ -270,7 +270,7 @@ This checklist serves as a comprehensive framework for validating infrastructure
|
||||
- [ ] Business stakeholders informed of changes
|
||||
- [ ] Feedback loops established for continuous improvement
|
||||
|
||||
## 11. BMAD WORKFLOW INTEGRATION
|
||||
## 11. BMad WORKFLOW INTEGRATION
|
||||
|
||||
### 11.1 Development Agent Alignment
|
||||
|
||||
|
||||
@@ -2,7 +2,7 @@ name: bmad-infrastructure-devops
|
||||
version: 1.2.0
|
||||
short-title: Infrastructure and DevOps capabilities
|
||||
description: >-
|
||||
This expansion pack extends BMAD Method with comprehensive infrastructure and
|
||||
This expansion pack extends BMad Method with comprehensive infrastructure and
|
||||
DevOps capabilities. It's designed for teams that need to define, implement,
|
||||
and manage cloud infrastructure alongside their application development.
|
||||
author: Brian (BMad)
|
||||
|
||||
@@ -55,13 +55,13 @@ To conduct a thorough review of existing infrastructure to identify improvement
|
||||
- Create an improvement roadmap with suggested timelines
|
||||
- Highlight cost optimization opportunities
|
||||
|
||||
### 5. BMAD Integration Assessment
|
||||
### 5. BMad Integration Assessment
|
||||
|
||||
- Evaluate how current infrastructure supports other BMAD agents:
|
||||
- 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
|
||||
- Document any gaps in BMad integration
|
||||
|
||||
### 6. Architectural Escalation Assessment
|
||||
|
||||
@@ -133,7 +133,7 @@ A comprehensive infrastructure review report that includes:
|
||||
2. **Prioritized findings** with severity ratings
|
||||
3. **Detailed recommendations** with effort/impact estimates
|
||||
4. **Cost optimization opportunities**
|
||||
5. **BMAD integration assessment**
|
||||
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)
|
||||
|
||||
@@ -2,7 +2,7 @@
|
||||
|
||||
## 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.
|
||||
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
|
||||
|
||||
@@ -82,9 +82,9 @@ To comprehensively validate platform infrastructure changes against security, re
|
||||
- Provide validation signoff recommendation based on complete platform assessment
|
||||
- Document platform component integration validation results
|
||||
|
||||
### 6. BMAD Integration Assessment
|
||||
### 6. BMad Integration Assessment
|
||||
|
||||
- Review how platform infrastructure changes support other BMAD agents:
|
||||
- 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
|
||||
@@ -128,7 +128,7 @@ A comprehensive platform validation report documenting:
|
||||
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
|
||||
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
|
||||
|
||||
|
||||
@@ -264,9 +264,9 @@ Create pipeline diagram showing:
|
||||
- Cost Monitoring & Reporting
|
||||
- Optimization Recommendations
|
||||
|
||||
## BMAD Integration Architecture
|
||||
## BMad Integration Architecture
|
||||
|
||||
[[LLM: Design infrastructure to specifically support other BMAD agents and their workflows. This ensures the infrastructure enables the entire BMAD methodology.]]
|
||||
[[LLM: Design infrastructure to specifically support other BMad agents and their workflows. This ensures the infrastructure enables the entire BMad methodology.]]
|
||||
|
||||
### Development Agent Support
|
||||
|
||||
|
||||
Reference in New Issue
Block a user