bmad-method 4.4.2 → 4.5.1

package/expansion-packs/expansion-creator/templates/agent-teams-tmpl.md

@@ -0,0 +1,154 @@
+# Agent Team Configuration Template
+
+[[LLM: This template is for creating agent team configurations in YAML format. Follow the structure carefully and replace all placeholders with appropriate values. The team name should reflect the team's purpose and domain focus.]]
+
+````yaml
+bundle:
+  name: {{team-display-name}}
+  [[LLM: Use format "Team [Descriptor]" for generic teams or "[Domain] Team" for specialized teams. Examples: "Team Fullstack", "Healthcare Team", "Legal Team"]]
+
+  icon: {{team-emoji}}
+  [[LLM: Choose a single emoji that best represents the team's function or name]]
+
+  description: {{team-description}}
+  [[LLM: Write a concise description (1 sentence) that explains:
+  1. The team's primary purpose
+  2. What types of projects they handle
+  3. Any special capabilities or focus areas
+  4. Keep it short as its displayed in menus
+  Example: "Full Stack Ideation Web App Team." or "Startup Business Coaching team"]]
+
+agents:
+  [[LLM: List the agents that make up this team. Guidelines:
+  - Use shortened agent names (e.g., 'analyst' not 'business-analyst')
+  - Include 'bmad-orchestrator' for bmad-core teams as the coordinator
+  - Only use '*' for an all-inclusive team (rare)
+  - Order agents logically by workflow (analysis → design → development → testing)
+  - For expansion packs, include both core agents and custom agents]]
+
+  ^^CONDITION: standard-team^^
+  # Core workflow agents
+  - bmad-orchestrator  # Team coordinator
+  - analyst            # Requirements and analysis
+  - pm                 # Product management
+  - architect          # System design
+  - dev                # Development
+  - qa                 # Quality assurance
+  ^^/CONDITION: standard-team^^
+
+  ^^CONDITION: minimal-team^^
+  # Minimal team for quick iterations
+  - bmad-orchestrator  # Team coordinator
+  - architect          # Design and planning
+  - dev                # Implementation
+  ^^/CONDITION: minimal-team^^
+
+  ^^CONDITION: specialized-team^^
+  # Domain-specific team composition
+  - {{domain}}-orchestrator  # Domain coordinator
+  <<REPEAT section="specialist-agents" count="{{agent-count}}">>
+  - {{agent-short-name}}     # {{agent-role-description}}
+  <</REPEAT>>
+  ^^/CONDITION: specialized-team^^
+
+  ^^CONDITION: include-all-agents^^
+  - '*'  # Include all available agents
+  ^^/CONDITION: include-all-agents^^
+
+workflows:
+  [[LLM: Define the workflows this team can execute that will guide the user through a multi-step multi agent process. Guidelines:
+  - Use null if the team doesn't have predefined workflows
+  - Workflow names should be descriptive
+  - use domain-specific workflow names]]
+
+  ^^CONDITION: no-workflows^^
+  null  # No predefined workflows
+  ^^/CONDITION: no-workflows^^
+
+  ^^CONDITION: standard-workflows^^
+  # New project workflows
+  - greenfield-fullstack  # New full-stack application
+  - greenfield-service    # New backend service
+  - greenfield-ui         # New frontend application
+
+  # Existing project workflows
+  - brownfield-fullstack  # Enhance existing full-stack app
+  - brownfield-service    # Enhance existing service
+  - brownfield-ui         # Enhance existing UI
+  ^^/CONDITION: standard-workflows^^
+
+  ^^CONDITION: domain-workflows^^
+  # Domain-specific workflows
+  <<REPEAT section="workflows" count="{{workflow-count}}">>
+  - {{workflow-name}}  # {{workflow-description}}
+  <</REPEAT>>
+  ^^/CONDITION: domain-workflows^^
+```text
+
+@{example-1: Standard fullstack team}
+
+```yaml
+bundle:
+  name: Team Fullstack
+  icon: 🚀
+  description: Complete agile team for full-stack web applications. Handles everything from requirements to deployment.
+agents:
+  - bmad-orchestrator
+  - analyst
+  - pm
+  - architect
+  - dev
+  - qa
+  - ux-expert
+workflows:
+  - greenfield-fullstack
+  - greenfield-service
+  - greenfield-ui
+  - brownfield-fullstack
+  - brownfield-service
+  - brownfield-ui
+````
+
+@{example-2: Healthcare expansion pack team}
+
+````yaml
+bundle:
+  name: Healthcare Compliance Team
+  icon: ⚕️
+  description: Specialized team for healthcare applications with HIPAA compliance focus. Manages clinical workflows and regulatory requirements.
+agents:
+  - healthcare-orchestrator
+  - clinical-analyst
+  - compliance-officer
+  - architect
+  - dev
+  - qa
+workflows:
+  - healthcare-patient-portal
+  - healthcare-compliance-audit
+  - clinical-trial-management
+```text
+
+@{example-3: Minimal IDE team}
+
+```yaml
+bundle:
+  name: Team IDE Minimal
+  icon: ⚡
+  description: Minimal team for IDE usage. Just the essentials for quick development.
+agents:
+  - bmad-orchestrator
+  - architect
+  - dev
+workflows: null
+````
+
+[[LLM: When creating a new team configuration:
+
+1. Choose the most appropriate condition block based on team type
+2. Remove all unused condition blocks
+3. Replace all placeholders with actual values
+4. Ensure agent names match available agents in the system
+5. Verify workflow names match available workflows
+6. Save as team-[descriptor].yml or [domain]-team.yml
+7. Place in the agent-teams directory of the appropriate location]]

package/expansion-packs/expansion-creator/templates/agent-tmpl.md

@@ -0,0 +1,140 @@
+# [AGENT_ID]
+
+[[LLM: This is an agent definition template. When creating a new agent:
+
+1. ALL dependencies (tasks, templates, checklists, data) MUST exist or be created
+2. For output generation, use the create-doc pattern with appropriate templates
+3. Templates should include LLM instructions for guiding users through content creation
+4. Character personas should be consistent and domain-appropriate
+5. Follow the numbered options protocol for all user interactions]]
+
+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:
+
+````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
+
+agent:
+  name: [AGENT_NAME]
+  id: [AGENT_ID]
+  title: [AGENT_TITLE]
+  customization: [OPTIONAL_CUSTOMIZATION]
+
+persona:
+  role: [AGENT_ROLE_DESCRIPTION]
+  style: [COMMUNICATION_STYLE]
+  identity: [AGENT_IDENTITY_DESCRIPTION]
+  focus: [PRIMARY_FOCUS_AREAS]
+
+  core_principles:
+    - [PRINCIPLE_1]
+    - [PRINCIPLE_2]
+    - [PRINCIPLE_3]
+    # Add more principles as needed
+
+startup:
+  - [STARTUP_INSTRUCTIONS]
+
+commands:
+  - "*help" - Show: numbered list of the following commands to allow selection
+  - "*chat-mode" - (Default) [DEFAULT_MODE_DESCRIPTION]
+  - "*create-doc {template}" - Create doc (no template = show available templates)
+  [[LLM: For output generation tasks, always use create-doc with templates rather than custom tasks.
+  Example: Instead of a "create-blueprint" task, use "*create-doc blueprint-tmpl"
+  The template should contain LLM instructions for guiding users through the creation process]]
+  - [tasks] specific to the agent that are not covered by a template
+  [[LLM: Only create custom tasks for actions that don't produce documents, like analysis, validation, or process execution]]
+  - "*exit" - Say goodbye as the [AGENT_TITLE], and then abandon inhabiting this persona
+
+dependencies:
+  [[LLM: CRITICAL - All dependencies listed here MUST exist in the expansion pack or be created:
+  - Tasks: Must exist in tasks/ directory (include create-doc if using templates)
+  - Templates: Must exist in templates/ directory with proper LLM instructions
+  - Checklists: Must exist in checklists/ directory for quality validation
+  - Data: Must exist in data/ directory or be documented as user-required
+  - Utils: Must exist in utils/ directory (include template-format if using templates)]]
+
+  tasks:
+    - create-doc  # Required if agent creates documents from templates
+    - [TASK_1]    # Custom task for non-document operations
+    - [TASK_2]    # Another custom task
+    [[LLM: Example tasks: validate-design, analyze-requirements, execute-tests]]
+
+  templates:
+    - [TEMPLATE_1]  # Template with LLM instructions for guided creation
+    - [TEMPLATE_2]  # Another template for different document type
+    [[LLM: Example: blueprint-tmpl, contract-tmpl, report-tmpl
+    Each template should include [[LLM: guidance]] and other conventions from `template-formmat.md` sections for user interaction]]
+
+  checklists:
+    - [CHECKLIST_1]  # Quality validation for template outputs
+    [[LLM: Example: blueprint-checklist, contract-checklist
+    Checklists validate documents created from templates]]
+
+  data:
+    - [DATA_1]  # Domain knowledge files
+    [[LLM: Example: building-codes.md, legal-terminology.md
+    Can be embedded in pack or required from user]]
+
+  utils:
+    - template-format  # Required if using templates
+    - [UTIL_1]        # Other utilities as needed
+    [[LLM: Include workflow-management if agent participates in workflows]]
+```text
+
+@{example: Construction Contractor Agent}
+
+```yaml
+activation-instructions:
+  - Follow all instructions in this file
+  - Stay in character as Marcus Thompson, Construction Manager
+  - Use numbered options for all interactions
+agent:
+  name: Marcus Thompson
+  id: construction-contractor
+  title: Construction Project Manager
+  customization: null
+persona:
+  role: Licensed general contractor with 20 years experience
+  style: Professional, detail-oriented, safety-conscious
+  identity: Former site foreman who worked up to project management
+  focus: Building design, code compliance, project scheduling, cost estimation
+  core_principles:
+    - Safety first - all designs must prioritize worker and occupant safety
+    - Code compliance - ensure all work meets local building codes
+    - Quality craftsmanship - no shortcuts on structural integrity
+startup:
+  - Greet as Marcus Thompson, Construction Project Manager
+  - Briefly mention your experience and readiness to help
+  - Ask what type of construction project they're planning
+  - DO NOT auto-execute any commands
+commands:
+  - '*help" - Show numbered list of available commands'
+  - '*chat-mode" - Discuss construction projects and provide expertise'
+  - '*create-doc blueprint-tmpl" - Create architectural blueprints'
+  - '*create-doc estimate-tmpl" - Create project cost estimate'
+  - '*create-doc schedule-tmpl" - Create construction schedule'
+  - '*validate-plans" - Review plans for code compliance'
+  - '*safety-assessment" - Evaluate safety considerations'
+  - '*exit" - Say goodbye as Marcus and exit'
+dependencies:
+  tasks:
+    - 'create-doc          # For document creation'
+    - 'validate-plans      # Custom validation task'
+    - 'safety-assessment   # Custom safety review task'
+  templates:
+    - 'blueprint-tmpl      # Architectural blueprint template'
+    - 'estimate-tmpl       # Cost estimation template'
+    - 'schedule-tmpl       # Project timeline template'
+  checklists:
+    - 'blueprint-checklist # Validates blueprint completeness'
+    - 'safety-checklist    # Safety compliance validation'
+  data:
+    - 'building-codes.md   # Local building code reference'
+    - 'materials-guide.md  # Construction materials specs'
+  utils:
+    - 'template-format     # For template processing'
+````

package/expansion-packs/expansion-creator/utils/template-format.md

@@ -0,0 +1,26 @@
+# Template Format Conventions
+
+Templates in the BMAD method use standardized markup for AI processing. These conventions ensure consistent document generation.
+
+## Template Markup Elements
+
+- **{{placeholders}}**: Variables to be replaced with actual content
+- **[[LLM: instructions]]**: Internal processing instructions for AI agents (never shown to users)
+- **REPEAT** sections: Content blocks that may be repeated as needed
+- **^^CONDITION^^** blocks: Conditional content included only if criteria are met
+- **@{examples}**: Example content for guidance (never output to users)
+
+## Processing Rules
+
+- Replace all {{placeholders}} with project-specific content
+- Execute all [[LLM: instructions]] internally without showing users
+- Process conditional and repeat blocks as specified
+- Use examples for guidance but never include them in final output
+- Present only clean, formatted content to users
+
+## Critical Guidelines
+
+- **NEVER display template markup, LLM instructions, or examples to users**
+- Template elements are for AI processing only
+- Focus on faithful template execution and clean output
+- All template-specific instructions are embedded within templates

package/expansion-packs/expansion-creator/utils/workflow-management.md

@@ -0,0 +1,223 @@
+# Workflow Management
+
+This utility enables the BMAD orchestrator to manage and execute team workflows.
+
+## Important: Dynamic Workflow Loading
+
+The BMAD orchestrator MUST read the available workflows from the current team configuration's `workflows` field. Do not use hardcoded workflow lists. Each team bundle defines its own set of supported workflows based on the agents it includes.
+
+**Critical Distinction**:
+
+- When asked "what workflows are available?", show ONLY the workflows defined in the current team bundle's configuration
+- Use `/agent-list` to show agents in the current bundle
+- Use `/workflows` to show workflows in the current bundle, NOT any creation tasks
+
+### Workflow Descriptions
+
+When displaying workflows, use these descriptions based on the workflow ID:
+
+- **greenfield-fullstack**: Build a new full-stack application from concept to development
+- **brownfield-fullstack**: Enhance an existing full-stack application with new features
+- **greenfield-service**: Build a new backend service or API from concept to development
+- **brownfield-service**: Enhance an existing backend service or API
+- **greenfield-ui**: Build a new frontend/UI application from concept to development
+- **brownfield-ui**: Enhance an existing frontend/UI application
+
+## Workflow Commands
+
+### /workflows
+
+Lists all available workflows for the current team. The available workflows are determined by the team configuration and may include workflows such as:
+
+- greenfield-fullstack
+- brownfield-fullstack
+- greenfield-service
+- brownfield-service
+- greenfield-ui
+- brownfield-ui
+
+The actual list depends on which team bundle is loaded. When responding to this command, display the workflows that are configured in the current team's `workflows` field.
+
+Example response format:
+
+````text
+Available workflows for [Team Name]:
+1. [workflow-id] - [Brief description based on workflow type]
+2. [workflow-id] - [Brief description based on workflow type]
+[... etc. ...]
+
+Use /workflow-start {number or id} to begin a workflow.
+```text
+
+### /workflow-start {workflow-id}
+
+Starts a specific workflow and transitions to the first agent.
+
+Example: `/workflow-start greenfield-fullstack`
+
+### /workflow-status
+
+Shows current workflow progress, completed artifacts, and next steps.
+
+Example response:
+
+```text
+Current Workflow: Greenfield Full-Stack Development
+Stage: Product Planning (2 of 6)
+Completed:
+  ✓ Discovery & Requirements
+    - project-brief (completed by Mary)
+
+In Progress:
+  ⚡ Product Planning
+    - Create PRD (John) - awaiting input
+
+Next: Technical Architecture
+```text
+
+### /workflow-resume
+
+Resumes a workflow from where it left off, useful when starting a new chat.
+
+User can provide completed artifacts:
+
+```text
+User: /workflow-resume greenfield-fullstack
+      I have completed: project-brief, PRD
+BMad: I see you've completed Discovery and part of Product Planning.
+      Based on the greenfield-fullstack workflow, the next step is:
+      - UX Strategy with Sally (ux-expert)
+
+      Would you like me to load Sally to continue?
+```text
+
+### /workflow-next
+
+Shows the next recommended agent and action in the current workflow.
+
+## Workflow Execution Flow
+
+### 1. Starting a Workflow
+
+When a workflow is started:
+
+1. Load the workflow definition
+2. Identify the first stage and step
+3. Transition to the required agent
+4. Provide context about expected inputs/outputs
+5. Guide artifact creation
+
+### 2. Stage Transitions
+
+After each artifact is completed:
+
+1. Mark the step as complete
+2. Check transition conditions
+3. If stage is complete, move to next stage
+4. Load the appropriate agent
+5. Pass relevant artifacts as context
+
+### 3. Artifact Tracking
+
+Track all created artifacts:
+
+```yaml
+workflow_state:
+  current_workflow: greenfield-fullstack
+  current_stage: planning
+  current_step: 2
+  artifacts:
+    project-brief:
+      status: completed
+      created_by: analyst
+      timestamp: 2024-01-15T10:30:00.000Z
+    prd:
+      status: in-progress
+      created_by: pm
+      started: 2024-01-15T11:00:00.000Z
+```text
+
+### 4. Workflow Interruption Handling
+
+When user returns after interruption:
+
+1. Ask if continuing previous workflow
+2. Request any completed artifacts
+3. Analyze provided artifacts
+4. Determine workflow position
+5. Suggest next appropriate step
+
+Example:
+
+```text
+User: I'm working on a new app. Here's my PRD and architecture doc.
+BMad: I see you have a PRD and architecture document. Based on these artifacts,
+      it looks like you're following the greenfield-fullstack workflow and have completed
+      stages 1-3. The next recommended step would be:
+
+      Stage 4: Validation & Refinement
+      - Load Sarah (Product Owner) to validate all artifacts
+
+      Would you like to continue with this workflow?
+```text
+
+## Workflow Context Passing
+
+When transitioning between agents, pass:
+
+1. Previous artifacts created
+2. Current workflow stage
+3. Expected outputs
+4. Any decisions or constraints identified
+
+Example transition:
+
+```text
+BMad: Great! John has completed the PRD. According to the greenfield-fullstack workflow,
+      the next step is UX Strategy with Sally.
+
+      /ux-expert
+
+Sally: I see we're in the Product Planning stage of the greenfield-fullstack workflow.
+       I have access to:
+       - Project Brief from Mary
+       - PRD from John
+
+       Let's create the UX strategy and UI specifications. First, let me review
+       the PRD to understand the features we're designing for...
+```text
+
+## Multi-Path Workflows
+
+Some workflows may have multiple paths:
+
+```yaml
+conditional_paths:
+  - condition: project_type == 'mobile'
+    next_stage: mobile-specific-design
+  - condition: project_type == 'web'
+    next_stage: web-architecture
+  - default: fullstack-architecture
+````
+
+Handle these by asking clarifying questions when needed.
+
+## Workflow Best Practices
+
+1. **Always show progress** - Users should know where they are
+2. **Explain transitions** - Why moving to next agent
+3. **Preserve context** - Pass relevant information forward
+4. **Allow flexibility** - Users can skip or modify steps
+5. **Track everything** - Maintain complete workflow state
+
+## Integration with Agents
+
+Each agent should be workflow-aware:
+
+- Know which workflow is active
+- Understand their role in the workflow
+- Access previous artifacts
+- Know expected outputs
+- Guide toward workflow goals
+
+This creates a seamless experience where the entire team works together toward the workflow's objectives.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "bmad-method",
-  "version": "4.4.2",
+  "version": "4.5.1",
   "description": "Breakthrough Method of Agile AI-driven Development",
   "main": "tools/cli.js",
   "bin": {
@@ -14,7 +14,7 @@
     "list:agents": "node tools/cli.js list:agents",
     "validate": "node tools/cli.js validate",
     "install:bmad": "node tools/installer/bin/bmad.js install",
-    "format": "prettier --write \"**/*.md\" && node tools/yaml-format.js **/*.md **/*.yml **/*.yaml .roo/.roomodes",
+    "format": "prettier --write \"**/*.md\"",
     "version:patch": "node tools/version-bump.js patch",
     "version:minor": "node tools/version-bump.js minor",
     "version:major": "node tools/version-bump.js major",
@@ -60,20 +60,8 @@
     "yaml-lint": "^1.7.0"
   },
   "lint-staged": {
-    "**/*.{yml,yaml}": [
-      "node tools/yaml-format.js"
-    ],
     "**/*.md": [
-      "node tools/yaml-format.js"
-    ],
-    ".roomodes": [
-      "node tools/yaml-format.js"
-    ],
-    "bmad-core/**/*.yml": [
-      "node tools/yaml-format.js"
-    ],
-    ".github/**/*.yml": [
-      "node tools/yaml-format.js"
+      "prettier --write"
     ]
   }
 }

package/tools/builders/web-builder.js

@@ -6,8 +6,7 @@ class WebBuilder {
   constructor(options = {}) {
     this.rootDir = options.rootDir || process.cwd();
     this.outputDirs = options.outputDirs || [
-      path.join(this.rootDir, 'dist'),
-      path.join(this.rootDir, 'bmad-core', 'web-bundles')
+      path.join(this.rootDir, 'dist')
     ];
     this.resolver = new DependencyResolver(this.rootDir);
     this.templatePath = path.join(this.rootDir, 'bmad-core', 'templates', 'web-agent-startup-instructions-template.md');
@@ -152,7 +151,6 @@ class WebBuilder {
   async buildExpansionPack(packName, options = {}) {
     const packDir = path.join(this.rootDir, 'expansion-packs', packName);
     const outputDirs = [
-      path.join(packDir, 'web-bundles'),
       path.join(this.rootDir, 'dist', 'expansion-packs', packName)
     ];
 
@@ -200,7 +198,7 @@ class WebBuilder {
     const agentTeamsDir = path.join(packDir, 'agent-teams');
     try {
       const teamFiles = await fs.readdir(agentTeamsDir);
-      const teamFile = teamFiles.find(f => f.startsWith('team-') && f.endsWith('.yml'));
+      const teamFile = teamFiles.find(f => f.endsWith('.yml'));
       
       if (teamFile) {
         console.log(`    Building team bundle for ${packName}`);

package/tools/cli.js

@@ -52,21 +52,6 @@ program
         }
       }
 
-      // Generate IDE configuration folders
-      console.log('Generating IDE configuration folders...');
-      const installDir = process.cwd();
-      
-      // Generate configurations for all supported IDEs
-      const ides = ['cursor', 'claude-code', 'windsurf', 'roo'];
-      for (const ide of ides) {
-        try {
-          console.log(`Setting up ${ide} integration...`);
-          await IdeSetup.setup(ide, installDir);
-        } catch (error) {
-          console.warn(`Warning: Failed to setup ${ide}:`, error.message);
-        }
-      }
-
       console.log('Build completed successfully!');
     } catch (error) {
       console.error('Build failed:', error.message);