bmad-method 4.4.2 → 4.5.1

package/bmad-core/templates/agent-tmpl.md

@@ -1,58 +0,0 @@
-# [AGENT_ID]
-
-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)
-  - [tasks] specific to the agent that are not covered by a template
-  - "*exit" - Say goodbye as the [AGENT_TITLE], and then abandon inhabiting this persona
-
-dependencies:
-  tasks:
-    - [TASK_1]
-    - [TASK_2]
-    # Add required tasks
-  templates:
-    - [TEMPLATE_1]
-    - [TEMPLATE_2]
-    # Add required templates
-  checklists:
-    - [CHECKLIST_1]
-    # Add required checklists
-  data:
-    - [DATA_1]
-    # Add required data files
-  utils:
-    - [UTIL_1]
-    # Add required utilities
-```

package/bmad-core/utils/agent-switcher.ide.md

@@ -1,112 +0,0 @@
-# Agent Switcher Instructions
-
-## Overview
-
-This document provides instructions for switching between different IDE agent personas in the BMAD-METHOD framework.
-
-## Behavior
-
-### Listing Available Agents
-
-When no agent name is provided:
-
-1. Read the `bmad-core/ide-agents/` directory
-2. Look for files matching the pattern `*.ide.md`
-3. Extract agent names from filenames (the part before `.ide.md`)
-4. Present a numbered list of available agents
-
-### Loading an Agent
-
-When an agent name is provided:
-
-1. Attempt to load `bmad-core/ide-agents/{agent-name}.ide.md`
-2. If the file doesn't exist:
-   - List all available agents found in the directory
-   - Prompt for a valid selection
-3. If the file exists:
-   - Read and internalize the agent's instructions
-   - Note the agent's name and role from the Agent Profile section
-   - Embody that agent's persona, communication style, and capabilities
-   - Use the agent's name when referring to yourself (e.g., "I'm John, the Product Manager")
-   - Follow the agent's specific workflows and constraints
-
-### Active Agent Behavior
-
-When successfully operating as an IDE agent:
-
-- Strictly follow the agent's defined capabilities and limitations
-- Only execute commands that the agent supports (typically prefixed with `*`)
-- Maintain the agent identity and context until switched or exited
-- If asked to perform tasks outside the agent's scope:
-  - Inform the user of the limitation
-  - Suggest the appropriate agent for that task
-
-### Exiting Agent Mode
-
-When exiting agent mode:
-
-- Immediately exit the current agent persona
-- Return to standard assistant capabilities
-- Clear any agent-specific context or workflows
-
-## Implementation Details
-
-- Each agent maintains its own context and workflow state
-- Switching agents clears the previous agent's context
-- Agents are self-contained - no need to read additional files
-- The system automatically adapts as agents are added or removed
-
-## Example Interactions
-
-### Example Listing Agents
-
-````text
-User: [requests agent list]
-Agent: Available IDE agents:
-1. architect
-2. dev
-3. devops
-4. pm
-5. po
-6. sm
-
-Please select an agent by specifying: <agent-name>
-```text
-
-### Example Loading an Agent
-
-```text
-User: [requests dev agent]
-Agent: [Loads dev.ide.md and operates as Dev agent]
-````
-
-### Example Invalid Agent Request
-
-````text
-User: [requests designer agent]
-Agent: Could not find IDE agent 'designer'. Available agents:
-1. architect
-2. dev
-3. devops
-4. pm
-5. po
-6. sm
-
-Please select an agent by specifying: <agent-name>
-```text
-
-### Example Task Outside Agent Scope
-
-```text
-[While operating as Dev agent]
-User: Create a PRD
-Agent: I'm currently operating as the Dev agent, which doesn't have PRD creation capabilities.
-The PM agent can create PRDs. Would you like me to switch to the PM agent?
-````
-
-### Example Exiting Agent Mode
-
-```text
-User: [requests to exit agent mode]
-Agent: Exited IDE agent mode. Returned to standard assistant capabilities.
-```

package/creator-tools/tasks/generate-expansion-pack.md

@@ -1,427 +0,0 @@
-# Create Expansion Pack Task
-
-This task helps you create a comprehensive BMAD expansion pack that can include new agents, tasks, templates, and checklists for a specific domain.
-
-## Understanding Expansion Packs
-
-Expansion packs extend BMAD with domain-specific capabilities. They are self-contained packages that can be installed into any BMAD project. Every expansion pack MUST include a custom BMAD orchestrator agent that manages the domain-specific workflow.
-
-## CRITICAL REQUIREMENTS
-
-1. **Create Planning Document First**: Before any implementation, create a concise task list for user approval
-2. **Verify All References**: Any task, template, or data file referenced in an agent MUST exist in the pack
-3. **Include Orchestrator**: Every pack needs a custom BMAD-style orchestrator agent
-4. **User Data Requirements**: Clearly specify any files users must provide in their data folder
-
-## Process Overview
-
-### Phase 1: Discovery and Planning
-
-#### 1.1 Define the Domain
-
-Ask the user:
-
-- **Pack Name**: Short identifier (e.g., `healthcare`, `fintech`, `gamedev`)
-- **Display Name**: Full name (e.g., "Healthcare Compliance Pack")
-- **Description**: What domain or industry does this serve?
-- **Key Problems**: What specific challenges will this pack solve?
-- **Target Users**: Who will benefit from this expansion?
-
-#### 1.2 Gather Examples
-
-Request from the user:
-
-- **Sample Documents**: Any existing documents in this domain
-- **Workflow Examples**: How work currently flows in this domain
-- **Compliance Needs**: Any regulatory or standards requirements
-- **Output Examples**: What final deliverables look like
-- **Data Requirements**: What reference data files users will need to provide
-
-#### 1.3 Create Planning Document
-
-IMPORTANT: STOP HERE AND CREATE PLAN FIRST
-
-Create `expansion-packs/{pack-name}/plan.md` with:
-
-````markdown
-# {Pack Name} Expansion Pack Plan
-
-## Overview
-
-- Pack Name: {name}
-- Description: {description}
-- Target Domain: {domain}
-
-## Components to Create
-
-### Agents
-
-- [ ] {pack-name}-orchestrator (REQUIRED: Custom BMAD orchestrator)
-- [ ] {agent-1-name}
-- [ ] {agent-2-name}
-
-### Tasks
-
-- [ ] {task-1} (referenced by: {agent})
-- [ ] {task-2} (referenced by: {agent})
-
-### Templates
-
-- [ ] {template-1} (used by: {agent/task})
-- [ ] {template-2} (used by: {agent/task})
-
-### Checklists
-
-- [ ] {checklist-1}
-- [ ] {checklist-2}
-
-### Data Files Required from User
-
-- [ ] {filename}.{ext} - {description of content needed}
-- [ ] {filename2}.{ext} - {description of content needed}
-
-## Approval
-
-User approval received: [ ] Yes
-
-````text
-
-Important: Wait for user approval before proceeding to Phase 2
-
-### Phase 2: Component Design
-
-#### 2.1 Create Orchestrator Agent
-
-**FIRST PRIORITY**: Design the custom BMAD orchestrator:
-
-- **Name**: `{pack-name}-orchestrator`
-- **Purpose**: Master coordinator for domain-specific workflow
-- **Key Commands**: Domain-specific orchestration commands
-- **Integration**: How it leverages other pack agents
-- **Workflow**: The complete process it manages
-
-#### 2.2 Identify Specialist Agents
-
-For each additional agent:
-
-- **Role**: What specialist is needed?
-- **Expertise**: Domain-specific knowledge required
-- **Interactions**: How they work with orchestrator and BMAD agents
-- **Unique Value**: What can't existing agents handle?
-- **Required Tasks**: List ALL tasks this agent references
-- **Required Templates**: List ALL templates this agent uses
-- **Required Data**: List ALL data files this agent needs
-
-#### 2.3 Design Specialized Tasks
-
-For each task:
-
-- **Purpose**: What specific action does it enable?
-- **Inputs**: What information is needed?
-- **Process**: Step-by-step instructions
-- **Outputs**: What gets produced?
-- **Agent Usage**: Which agents will use this task?
-
-#### 2.4 Create Document Templates
-
-For each template:
-
-- **Document Type**: What kind of document?
-- **Structure**: Sections and organization
-- **Placeholders**: Variable content areas
-- **Instructions**: How to complete each section
-- **Standards**: Any format requirements
-
-#### 2.5 Define Checklists
-
-For each checklist:
-
-- **Purpose**: What quality aspect does it verify?
-- **Scope**: When should it be used?
-- **Items**: Specific things to check
-- **Criteria**: Pass/fail conditions
-
-### Phase 3: Implementation
-
-IMPORTANT: Only proceed after plan.md is approved
-
-#### 3.1 Create Directory Structure
-
-```text
-expansion-packs/
-└── {pack-name}/
-    ├── plan.md (ALREADY CREATED)
-    ├── manifest.yml
-    ├── README.md
-    ├── agents/
-    │   ├── {pack-name}-orchestrator.yml (REQUIRED)
-    │   └── {agent-id}.yml
-    ├── personas/
-    │   ├── {pack-name}-orchestrator.md (REQUIRED)
-    │   └── {agent-id}.md
-    ├── tasks/
-    │   └── {task-name}.md
-    ├── templates/
-    │   └── {template-name}.md
-    ├── checklists/
-    │   └── {checklist-name}.md
-    └── ide-agents/
-        ├── {pack-name}-orchestrator.ide.md (REQUIRED)
-        └── {agent-id}.ide.md
-````
-````
-
-#### 3.2 Create Manifest
-
-Create `manifest.yml`:
-
-````yaml
-name: {pack-name}
-version: 1.0.0
-description: >-
-  {Detailed description of the expansion pack}
-author: {Your name or organization}
-bmad_version: "4.0.0"
-
-# Files to create in the expansion pack
-files:
-  agents:
-    - {pack-name}-orchestrator.yml
-    - {agent-name}.yml
-
-  personas:
-    - {pack-name}-orchestrator.md
-    - {agent-name}.md
-
-  ide-agents:
-    - {pack-name}-orchestrator.ide.md
-    - {agent-name}.ide.md
-
-  tasks:
-    - {task-name}.md
-
-  templates:
-    - {template-name}.md
-
-  checklists:
-    - {checklist-name}.md
-
-# Data files users must provide
-required_data:
-  - filename: {data-file}.{ext}
-    description: {What this file should contain}
-    location: bmad-core/data/
-
-# Dependencies on core BMAD components
-dependencies:
-  - {core-agent-name}
-  - {core-task-name}
-
-# Post-install message
-post_install_message: |
-  {Pack Name} expansion pack ready!
-
-  Required data files:
-  - {data-file}.{ext}: {description}
-
-  To use: npm run agent {pack-name}-orchestrator
-```text
-
-### Phase 4: Content Creation
-
-IMPORTANT: Work through plan.md checklist systematically!
-
-#### 4.1 Create Orchestrator First
-
-1. Create `personas/{pack-name}-orchestrator.md` with BMAD-style commands
-2. Create `agents/{pack-name}-orchestrator.yml` configuration
-3. Create `ide-agents/{pack-name}-orchestrator.ide.md`
-4. Verify ALL referenced tasks exist
-5. Verify ALL referenced templates exist
-6. Document data file requirements
-
-#### 4.2 Agent Creation Order
-
-For each additional agent:
-
-1. Create persona file with domain expertise
-2. Create agent configuration YAML
-3. Create IDE-optimized version
-4. **STOP** - Verify all referenced tasks/templates exist
-5. Create any missing tasks/templates immediately
-6. Mark agent as complete in plan.md
-
-#### 4.3 Task Creation Guidelines
-
-Each task should:
-
-1. Have a clear, single purpose
-2. Include step-by-step instructions
-3. Provide examples when helpful
-4. Reference domain standards
-5. Be reusable across agents
-
-#### 4.4 Template Best Practices
-
-Templates should:
-
-1. Include clear section headers
-2. Provide inline instructions
-3. Show example content
-4. Mark required vs optional sections
-5. Include domain-specific terminology
-
-### Phase 5: Verification and Documentation
-
-#### 5.1 Final Verification Checklist
-
-Before declaring complete:
-
-1. [ ] All items in plan.md marked complete
-2. [ ] Orchestrator agent created and tested
-3. [ ] All agent references validated
-4. [ ] All required data files documented
-5. [ ] manifest.yml lists all components
-6. [ ] No orphaned tasks or templates
-
-#### 5.2 Create README
-
-Include:
-
-- Overview of the pack's purpose
-- **Orchestrator usage instructions**
-- Required data files and formats
-- List of all components
-- Integration with BMAD workflow
-- Example scenarios
-
-#### 5.3 Data File Documentation
-
-For each required data file:
-
-```markdown
-## Required Data Files
-
-### {filename}.{ext}
-
-- **Purpose**: {why this file is needed}
-- **Format**: {file format and structure}
-- **Location**: Place in `bmad-core/data/`
-- **Example**:
-````
-
-## Example: Healthcare Expansion Pack
-
-```text
-healthcare/
-├── plan.md (Created first for approval)
-├── manifest.yml
-├── README.md
-├── agents/
-│   ├── healthcare-orchestrator.yml (REQUIRED)
-│   ├── clinical-analyst.yml
-│   └── compliance-officer.yml
-├── personas/
-│   ├── healthcare-orchestrator.md (REQUIRED)
-│   ├── clinical-analyst.md
-│   └── compliance-officer.md
-├── ide-agents/
-│   ├── healthcare-orchestrator.ide.md (REQUIRED)
-│   ├── clinical-analyst.ide.md
-│   └── compliance-officer.ide.md
-├── tasks/
-│   ├── hipaa-assessment.md
-│   ├── clinical-protocol-review.md
-│   └── patient-data-analysis.md
-├── templates/
-│   ├── clinical-trial-protocol.md
-│   ├── hipaa-compliance-report.md
-│   └── patient-outcome-report.md
-└── checklists/
-    ├── hipaa-checklist.md
-    └── clinical-data-quality.md
-
-Required user data files:
-- bmad-core/data/medical-terminology.md
-- bmad-core/data/hipaa-requirements.md
-```
-
-## Interactive Questions Flow
-
-### Initial Discovery
-
-1. "What domain or industry will this expansion pack serve?"
-2. "What are the main challenges or workflows in this domain?"
-3. "Do you have any example documents or outputs? (Please share)"
-4. "What specialized roles/experts exist in this domain?"
-5. "What reference data will users need to provide?"
-
-### Planning Phase
-
-1. "Here's the proposed plan. Please review and approve before we continue."
-
-### Orchestrator Design
-
-1. "What key commands should the {pack-name} orchestrator support?"
-2. "What's the typical workflow from start to finish?"
-3. "How should it integrate with core BMAD agents?"
-
-### Agent Planning
-
-1. "For agent '{name}', what is their specific expertise?"
-2. "What tasks will this agent reference? (I'll create them)"
-3. "What templates will this agent use? (I'll create them)"
-4. "What data files will this agent need? (You'll provide these)"
-
-### Task Design
-
-1. "Describe the '{task}' process step-by-step"
-2. "What information is needed to complete this task?"
-3. "What should the output look like?"
-
-### Template Creation
-
-1. "What sections should the '{template}' document have?"
-2. "Are there any required formats or standards?"
-3. "Can you provide an example of a completed document?"
-
-### Data Requirements
-
-1. "For {data-file}, what information should it contain?"
-2. "What format should this data be in?"
-3. "Can you provide a sample?"
-
-## Important Considerations
-
-- **Plan First**: ALWAYS create and get approval for plan.md before implementing
-- **Orchestrator Required**: Every pack MUST have a custom BMAD orchestrator
-- **Verify References**: ALL referenced tasks/templates MUST exist
-- **Document Data Needs**: Clearly specify what users must provide
-- **Domain Expertise**: Ensure accuracy in specialized fields
-- **Compliance**: Include necessary regulatory requirements
-
-## Tips for Success
-
-1. **Plan Thoroughly**: The plan.md prevents missing components
-2. **Build Orchestrator First**: It defines the overall workflow
-3. **Verify As You Go**: Check off items in plan.md
-4. **Test References**: Ensure no broken dependencies
-5. **Document Data**: Users need clear data file instructions
-
-## Common Mistakes to Avoid
-
-1. **Missing Orchestrator**: Every pack needs its own BMAD-style orchestrator
-2. **Orphaned References**: Agent references task that doesn't exist
-3. **Unclear Data Needs**: Not specifying required user data files
-4. **Skipping Plan**: Going straight to implementation
-5. **Generic Orchestrator**: Not making it domain-specific
-
-## Completion Checklist
-
-- [ ] plan.md created and approved
-- [ ] All plan.md items checked off
-- [ ] Orchestrator agent created
-- [ ] All agent references verified
-- [ ] Data requirements documented or added
-- [ ] README includes all setup instructions
-- [ ] manifest.yml reflects actual files

package/expansion-packs/bmad-2d-phaser-game-dev/agent-teams/team-game-dev.yml

@@ -1,12 +0,0 @@
-bundle:
-  name: Game Development Team
-  icon: 🎮
-  description: Comprehensive game development team specialized in 2D games using Phaser 3 and TypeScript. This team handles the complete game development lifecycle from initial concept brainstorming through detailed design documentation to technical implementation and quality assurance. Specializes in indie games, mobile games, web games, educational games, prototyping, and game feature development with focus on player experience and performance optimization.
-agents:
-  - bmad-orchestrator
-  - game-designer
-  - game-developer
-  - game-sm
-workflows:
-  - game-dev-greenfield
-  - game-prototype