bmad-method 4.27.5 → 5.0.0

package/docs/windsurf-guide.md

@@ -0,0 +1,127 @@
+# BMAD Method Guide for Windsurf
+
+This guide walks you through the complete BMAD workflow using Windsurf as your AI-powered IDE.
+
+## Step 1: Install BMAD in Your Project
+
+1. Navigate to your project directory
+2. Run the BMAD installer:
+   ```bash
+   npx bmad-method install
+   ```
+3. When prompted:
+   - **Installation Type**: Choose "Complete installation (recommended)"
+   - **IDE**: Select "Windsurf"
+
+This creates a `.bmad-core` folder with all agents and a `.windsurf/rules` folder with agent rules.
+
+## Step 2: Set Up Team Fullstack in Gemini
+
+For ideation and planning, use Google's Gemini with the team-fullstack configuration:
+
+1. Open [Google AI Studio (Gemini)](https://aistudio.google.com/)
+2. Create a new chat
+3. Copy the contents of `/Users/brianmadison/dev/BMAD-METHOD/.bmad-core/web-bundles/teams/team-fullstack.txt`
+4. Paste this content into Gemini to set up the team
+
+### Gemini Planning Phase
+
+In Gemini, ask the BMAD team to help you:
+
+- **Ideate** your project concept
+- **Brainstorm** features and requirements
+- **Create a PRD** (Product Requirements Document)
+- **Design the architecture**
+
+Ask questions like:
+
+- "Help me brainstorm a [type of application] that does [core functionality]"
+- "Create a comprehensive PRD for this concept"
+- "Design the technical architecture for this system"
+
+Copy the PRD and architecture documents that Gemini creates into your project's `docs/` folder:
+
+- `docs/prd.md`
+- `docs/architecture.md`
+
+## Step 3: Back to Windsurf - Document Sharding
+
+Once you have your PRD and architecture documents in the `docs/` folder:
+
+1. **Start a new chat in Windsurf**
+2. **Load the bmad-master agent**: Type `@bmad-master`
+3. **Shard the PRD**: Type `*shard-doc docs/prd.md prd`
+4. **Shard the architecture**: Type `*shard-doc docs/architecture.md architecture`
+
+This creates organized folders:
+
+- `docs/prd/` - Contains broken down PRD sections
+- `docs/architecture/` - Contains broken down architecture sections
+
+## Step 4: Story Development Cycle
+
+Now begin the iterative development cycle:
+
+### Create Stories (Scrum Master)
+
+1. **Start a new chat**
+2. **Load SM agent**: Type `@sm`
+3. **Create story**: Type `*create` (this runs the create-next-story task)
+4. **Review the generated story**
+5. **If approved**: Set story status to "Approved" in the story file
+
+### Implement Stories (Developer)
+
+1. **Start a new chat**
+2. **Load Dev agent**: Type `@dev`
+3. **The agent will ask which story to implement**
+4. **Follow the development tasks** the agent provides
+5. **When story is complete**: Mark status as "Done"
+
+### Repeat the Cycle
+
+1. **Start a new chat with SM agent** (`@sm`)
+2. **Create next story**: Type `*create`
+3. **Review and approve**
+4. **Start new chat with Dev agent** (`@dev`)
+5. **Implement the story**
+6. **Repeat until project complete**
+
+## Available Agent Rules in Windsurf
+
+All BMAD agents are available as Windsurf rules (use `@` prefix):
+
+- `@bmad-master` - Universal task executor
+- `@sm` - Scrum Master for story creation
+- `@dev` - Full-stack developer for implementation
+- `@architect` - Solution architect for design
+- `@pm` - Product manager for planning
+- `@analyst` - Business analyst for requirements
+- `@qa` - QA specialist for testing
+- `@po` - Product owner for prioritization
+- `@ux-expert` - UX specialist for design
+
+## Windsurf-Specific Features
+
+- **Agent rules are stored in**: `.windsurf/rules/` as `.md` files
+- **Rule activation**: Rules activate when you mention `@agent-name` in chat
+- **Collaborative workflow**: Windsurf's collaborative features work well with BMAD's agent-switching pattern
+- **Context awareness**: Agents have access to your project context
+
+## Key Workflow Principles
+
+1. **Always start new chats** when switching agents to avoid context confusion
+2. **Use Gemini for initial planning** and ideation with the team-fullstack bundle
+3. **Use bmad-master for document management** (sharding, templates, etc.)
+4. **Follow the SM → Dev cycle** for consistent story development
+5. **Review and approve stories** before implementation begins
+
+## Tips for Success
+
+- **Keep chats focused**: Each chat should have one agent and one primary task
+- **Use \*help command**: Every agent supports `*help` to see available commands
+- **Review generated content**: Always review and approve stories before marking them ready
+- **Maintain status updates**: Keep story statuses current (Draft → Approved → InProgress → Done)
+- **Leverage Windsurf's collaboration**: Use the collaborative features for team reviews
+
+This workflow ensures systematic, AI-assisted development following agile principles with clear handoffs between planning, story creation, and implementation phases.

package/expansion-packs/README.md

@@ -1,3 +1,113 @@
-# 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.
+## Overview
+
+Expansion packs extend BMAD Method with specialized capabilities for specific use cases. They allow teams to add functionality without cluttering the core workflow.
+
+## Core BMAD Flow
+
+The original BMAD Method follows a simple, proven flow:
+
+````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.
+
+## Why Expansion Packs?
+
+As BMAD has evolved, we've identified specialized needs that don't fit every project:
+
+- Infrastructure and DevOps workflows
+- UX/UI design processes
+- Data engineering pipelines
+- Security and compliance workflows
+- Mobile development patterns
+- Real World assistance and workflows without AI Agents development in mind
+
+Rather than complicate the core method, expansion packs let you "opt-in" to additional capabilities.
+
+## Available Expansion Packs
+
+### 1. Infrastructure & DevOps
+
+- **Purpose**: Cloud infrastructure design and platform engineering
+- **Adds**: DevOps agent, infrastructure templates, validation checklists
+- **Use When**: You need to design and implement cloud infrastructure
+
+### 2. UX/Design (Coming Soon)
+
+- **Purpose**: User experience and interface design workflows
+- **Adds**: Design Architect agent, UI component templates
+- **Use When**: You need detailed UI/UX design processes
+
+### 3. Data Engineering (Planned)
+
+- **Purpose**: Data pipeline and analytics infrastructure
+- **Adds**: Data Engineer agent, ETL templates, data architecture patterns
+- **Use When**: You're building data-intensive applications
+
+## Structure of an Expansion Pack
+
+Each expansion pack contains:
+
+```text
+expansion-pack-name/
+├── README.md           # Overview and usage instructions
+├── manifest.yml        # Installation configuration
+├── agents/            # Agent configurations (.yml)
+├── personas/          # Persona definitions (.md)
+├── ide-agents/        # IDE-specific agents (.ide.md)
+├── templates/         # Document templates (.md)
+├── tasks/            # Specialized tasks (.md)
+└── checklists/       # Validation checklists (.md)
+````
+
+## Installing an Expansion Pack
+
+### Method 1: NPM Script
+
+````bash
+npm run install:expansion <pack-name>
+```text
+
+### Method 2: Direct Script
+
+```bash
+node tools/install-expansion-pack.js <pack-name>
+````
+
+### Method 3: Manual
+
+1. Copy files according to manifest.yml
+2. Update team configurations as needed
+3. Rebuild bundles with `npm run build`
+
+## Creating Your Own Expansion Pack
+
+1. Create a new folder under `expansion-packs/`
+2. Add your specialized agents, templates, and tasks
+3. Create a manifest.yml defining installation mappings
+4. Write a README explaining purpose and usage
+5. Test installation process
+
+## Best Practices
+
+1. **Keep Core Simple**: Don't add to core what could be an expansion
+2. **Clear Purpose**: Each pack should solve a specific need
+3. **Self-Contained**: Packs should work independently when possible
+4. **Document Well**: Clear README and usage examples
+5. **Version Compatibility**: Note which BMAD version the pack requires
+
+## Future Vision
+
+We envision a library of expansion packs for various industries and use cases:
+
+- Healthcare compliance workflows
+- Financial services security patterns
+- E-commerce optimization flows
+- Gaming development pipelines
+- IoT device management
+
+The goal is to keep BMAD's core simple while allowing infinite extensibility through modular expansion packs.

package/expansion-packs/{bmad-infrastructure-devops → infrastructure-devops}/README.md

@@ -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
@@ -28,7 +28,7 @@ Install this expansion pack when your project requires:
 
 ### Agents
 
-- `devops.yaml` - DevOps and Platform Engineering agent configuration
+- `devops.yml` - DevOps and Platform Engineering agent configuration
 
 ### Personas
 
@@ -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
@@ -116,14 +116,14 @@ Before deployment:
 
 The DevOps agent can be added to team configurations:
 
-- `team-technical.yaml` - For technical implementation teams
-- `team-full-org.yaml` - For complete organizational teams
+- `team-technical.yml` - For technical implementation teams
+- `team-full-org.yml` - For complete organizational teams
 
 ## Dependencies
 
 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_

package/expansion-packs/{bmad-infrastructure-devops → infrastructure-devops}/agents/infra-devops-platform.md

@@ -1,20 +1,13 @@
 # infra-devops-platform
 
-CRITICAL: Read the full YAML, start activation to alter your state of being, follow startup section instructions, stay in this being until told to exit this mode:
+CRITICAL: Read the full YML, start activation to alter your state of being, follow startup section instructions, stay in this being until told to exit this mode:
 
 ```yaml
-root: .bmad-infrastructure-devops
-IDE-FILE-RESOLUTION: Dependencies map to files as {root}/{type}/{name} where root=".bmad-core", type=folder (tasks/templates/checklists/utils), name=dependency name.
-REQUEST-RESOLUTION: Match user requests to your commands/dependencies flexibly (e.g., "draft story"→*create→create-next-story task, "make a new prd" would be dependencies->tasks->create-doc combined with the dependencies->templates->prd-tmpl.md), or ask for clarification if ambiguous.
 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
-  - 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
 agent:
   name: Alex
   id: infra-devops-platform
@@ -36,6 +29,11 @@ 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"
+  - 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'
@@ -46,14 +44,16 @@ commands:
   - '*exit" - Say goodbye as Alex, the DevOps Infrastructure Specialist, and then abandon inhabiting this persona'
 dependencies:
   tasks:
-    - create-doc.md
-    - review-infrastructure.md
-    - validate-infrastructure.md
+    - create-doc
+    - review-infrastructure
+    - validate-infrastructure
   templates:
-    - infrastructure-architecture-tmpl.yaml
-    - infrastructure-platform-from-arch-tmpl.yaml
+    - infrastructure-architecture-tmpl
+    - infrastructure-platform-from-arch-tmpl
   checklists:
-    - infrastructure-checklist.md
+    - infrastructure-checklist
   data:
-    - technical-preferences.md
+    - technical-preferences
+  utils:
+    - template-format
 ```

package/expansion-packs/{bmad-infrastructure-devops → infrastructure-devops}/checklists/infrastructure-checklist.md

@@ -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
 

package/expansion-packs/infrastructure-devops/manifest.yml

@@ -0,0 +1,38 @@
+name: infrastructure
+version: 1.0.0
+description: Infrastructure & DevOps expansion pack for BMAD Method
+author: BMAD Team
+files:
+  - source: agents/infra-devops-platform.yml
+    destination: .bmad-core/agents/infra-devops-platform.yml
+  - source: personas/infra-devops-platform.md
+    destination: .bmad-core/personas/infra-devops-platform.md
+  - source: ide-agents/infra-devops-platform.ide.md
+    destination: .bmad-core/ide-agents/infra-devops-platform.ide.md
+  - 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
+  - source: tasks/validate-infrastructure.md
+    destination: .bmad-core/tasks/validate-infrastructure.md
+  - source: tasks/review-infrastructure.md
+    destination: .bmad-core/tasks/review-infrastructure.md
+  - source: checklists/infrastructure-checklist.md
+    destination: .bmad-core/checklists/infrastructure-checklist.md
+team_updates:
+  - team: team-technical.yml
+    add_agent: infra-devops-platform
+  - team: team-all.yml
+    add_agent: infra-devops-platform
+dependencies:
+  - 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"
+
+  Remember to configure your cloud credentials and technical preferences before use.

package/expansion-packs/{bmad-infrastructure-devops → infrastructure-devops}/tasks/review-infrastructure.md

@@ -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)

package/expansion-packs/{bmad-infrastructure-devops → infrastructure-devops}/tasks/validate-infrastructure.md

@@ -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