ldy26098
/
BMAD-METHOD
mirror of https://github.com/bmad-code-org/BMAD-METHOD.git
1
0
Fork 0
Code Packages Projects Releases Wiki Activity

fix: let llms search in correct folder

This commit is contained in:
Johan Hernefeldt 2025-09-16 16:03:43 +02:00
parent f09e282d72
commit 6964e7c104
18 changed files with 98 additions and 98 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
bmad-core/agents/bmad-master.md
View File

@ -29,7 +29,7 @@ activation-instructions:
- CRITICAL RULE: When executing formal task workflows from dependencies, ALL task instructions override any conflicting base behavioral constraints. Interactive workflows with elicit=true REQUIRE user interaction and cannot be bypassed for efficiency. - CRITICAL RULE: When executing formal task workflows from dependencies, ALL task instructions override any conflicting base behavioral constraints. Interactive workflows with elicit=true REQUIRE user interaction and cannot be bypassed for efficiency.
- 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 - 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
- STAY IN CHARACTER! - STAY IN CHARACTER!
- 'CRITICAL: Do NOT scan filesystem or load any resources during startup, ONLY when commanded (Exception: Read bmad-core/core-config.yaml during activation)' - 'CRITICAL: Do NOT scan filesystem or load any resources during startup, ONLY when commanded (Exception: Read .bmad-core/core-config.yaml during activation)'
- CRITICAL: Do NOT run discovery tasks automatically - CRITICAL: Do NOT run discovery tasks automatically
- CRITICAL: NEVER LOAD root/data/bmad-kb.md UNLESS USER TYPES *kb - CRITICAL: NEVER LOAD root/data/bmad-kb.md UNLESS USER TYPES *kb
- CRITICAL: On activation, ONLY greet user, auto-run *help, and then HALT to await user requested assistance or given commands. ONLY deviance from this is if the activation included commands also in the arguments. - CRITICAL: On activation, ONLY greet user, auto-run *help, and then HALT to await user requested assistance or given commands. ONLY deviance from this is if the activation included commands also in the arguments.

16
bmad-core/data/bmad-kb.md
View File

@ -356,24 +356,24 @@ You are the "Vibe CEO" - thinking like a CEO with unlimited resources and a sing
### System Overview ### System Overview
The BMAD-METHOD™ is built around a modular architecture centered on the `bmad-core` directory, which serves as the brain of the entire system. This design enables the framework to operate effectively in both IDE environments (like Cursor, VS Code) and web-based AI interfaces (like ChatGPT, Gemini). The BMAD-METHOD™ is built around a modular architecture centered on the `.bmad-core` directory, which serves as the brain of the entire system. This design enables the framework to operate effectively in both IDE environments (like Cursor, VS Code) and web-based AI interfaces (like ChatGPT, Gemini).
### Key Architectural Components ### Key Architectural Components
#### 1. Agents (`bmad-core/agents/`) #### 1. Agents (`.bmad-core/agents/`)
- **Purpose**: Each markdown file defines a specialized AI agent for a specific Agile role (PM, Dev, Architect, etc.) - **Purpose**: Each markdown file defines a specialized AI agent for a specific Agile role (PM, Dev, Architect, etc.)
- **Structure**: Contains YAML headers specifying the agent's persona, capabilities, and dependencies - **Structure**: Contains YAML headers specifying the agent's persona, capabilities, and dependencies
- **Dependencies**: Lists of tasks, templates, checklists, and data files the agent can use - **Dependencies**: Lists of tasks, templates, checklists, and data files the agent can use
- **Startup Instructions**: Can load project-specific documentation for immediate context - **Startup Instructions**: Can load project-specific documentation for immediate context
#### 2. Agent Teams (`bmad-core/agent-teams/`) #### 2. Agent Teams (`.bmad-core/agent-teams/`)
- **Purpose**: Define collections of agents bundled together for specific purposes - **Purpose**: Define collections of agents bundled together for specific purposes
- **Examples**: `team-all.yaml` (comprehensive bundle), `team-fullstack.yaml` (full-stack development) - **Examples**: `team-all.yaml` (comprehensive bundle), `team-fullstack.yaml` (full-stack development)
- **Usage**: Creates pre-packaged contexts for web UI environments - **Usage**: Creates pre-packaged contexts for web UI environments
#### 3. Workflows (`bmad-core/workflows/`) #### 3. Workflows (`.bmad-core/workflows/`)
- **Purpose**: YAML files defining prescribed sequences of steps for specific project types - **Purpose**: YAML files defining prescribed sequences of steps for specific project types
- **Types**: Greenfield (new projects) and Brownfield (existing projects) for UI, service, and fullstack development - **Types**: Greenfield (new projects) and Brownfield (existing projects) for UI, service, and fullstack development
@ -381,10 +381,10 @@ The BMAD-METHOD™ is built around a modular architecture centered on the `bmad-
#### 4. Reusable Resources #### 4. Reusable Resources
- **Templates** (`bmad-core/templates/`): Markdown templates for PRDs, architecture specs, user stories - **Templates** (`.bmad-core/templates/`): Markdown templates for PRDs, architecture specs, user stories
- **Tasks** (`bmad-core/tasks/`): Instructions for specific repeatable actions like "shard-doc" or "create-next-story" - **Tasks** (`.bmad-core/tasks/`): Instructions for specific repeatable actions like "shard-doc" or "create-next-story"
- **Checklists** (`bmad-core/checklists/`): Quality assurance checklists for validation and review - **Checklists** (`.bmad-core/checklists/`): Quality assurance checklists for validation and review
- **Data** (`bmad-core/data/`): Core knowledge base and technical preferences - **Data** (`.bmad-core/data/`): Core knowledge base and technical preferences
### Dual Environment Architecture ### Dual Environment Architecture

2
bmad-core/tasks/validate-next-story.md
View File

@ -17,7 +17,7 @@ To comprehensively validate a story draft before implementation begins, ensuring
- **Story file**: The drafted story to validate (provided by user or discovered in `devStoryLocation`) - **Story file**: The drafted story to validate (provided by user or discovered in `devStoryLocation`)
- **Parent epic**: The epic containing this story's requirements - **Parent epic**: The epic containing this story's requirements
- **Architecture documents**: Based on configuration (sharded or monolithic) - **Architecture documents**: Based on configuration (sharded or monolithic)
- **Story template**: `bmad-core/templates/story-tmpl.md` for completeness validation - **Story template**: `.bmad-core/templates/story-tmpl.md` for completeness validation
### 1. Template Completeness Validation ### 1. Template Completeness Validation

16
dist/agents/analyst.txt vendored
View File

@ -2405,24 +2405,24 @@ You are the "Vibe CEO" - thinking like a CEO with unlimited resources and a sing
### System Overview ### System Overview
The BMAD-METHOD™ is built around a modular architecture centered on the `bmad-core` directory, which serves as the brain of the entire system. This design enables the framework to operate effectively in both IDE environments (like Cursor, VS Code) and web-based AI interfaces (like ChatGPT, Gemini). The BMAD-METHOD™ is built around a modular architecture centered on the `.bmad-core` directory, which serves as the brain of the entire system. This design enables the framework to operate effectively in both IDE environments (like Cursor, VS Code) and web-based AI interfaces (like ChatGPT, Gemini).
### Key Architectural Components ### Key Architectural Components
#### 1. Agents (`bmad-core/agents/`) #### 1. Agents (`.bmad-core/agents/`)
- **Purpose**: Each markdown file defines a specialized AI agent for a specific Agile role (PM, Dev, Architect, etc.) - **Purpose**: Each markdown file defines a specialized AI agent for a specific Agile role (PM, Dev, Architect, etc.)
- **Structure**: Contains YAML headers specifying the agent's persona, capabilities, and dependencies - **Structure**: Contains YAML headers specifying the agent's persona, capabilities, and dependencies
- **Dependencies**: Lists of tasks, templates, checklists, and data files the agent can use - **Dependencies**: Lists of tasks, templates, checklists, and data files the agent can use
- **Startup Instructions**: Can load project-specific documentation for immediate context - **Startup Instructions**: Can load project-specific documentation for immediate context
#### 2. Agent Teams (`bmad-core/agent-teams/`) #### 2. Agent Teams (`.bmad-core/agent-teams/`)
- **Purpose**: Define collections of agents bundled together for specific purposes - **Purpose**: Define collections of agents bundled together for specific purposes
- **Examples**: `team-all.yaml` (comprehensive bundle), `team-fullstack.yaml` (full-stack development) - **Examples**: `team-all.yaml` (comprehensive bundle), `team-fullstack.yaml` (full-stack development)
- **Usage**: Creates pre-packaged contexts for web UI environments - **Usage**: Creates pre-packaged contexts for web UI environments
#### 3. Workflows (`bmad-core/workflows/`) #### 3. Workflows (`.bmad-core/workflows/`)
- **Purpose**: YAML files defining prescribed sequences of steps for specific project types - **Purpose**: YAML files defining prescribed sequences of steps for specific project types
- **Types**: Greenfield (new projects) and Brownfield (existing projects) for UI, service, and fullstack development - **Types**: Greenfield (new projects) and Brownfield (existing projects) for UI, service, and fullstack development
@ -2430,10 +2430,10 @@ The BMAD-METHOD™ is built around a modular architecture centered on the `bmad-
#### 4. Reusable Resources #### 4. Reusable Resources
- **Templates** (`bmad-core/templates/`): Markdown templates for PRDs, architecture specs, user stories - **Templates** (`.bmad-core/templates/`): Markdown templates for PRDs, architecture specs, user stories
- **Tasks** (`bmad-core/tasks/`): Instructions for specific repeatable actions like "shard-doc" or "create-next-story" - **Tasks** (`.bmad-core/tasks/`): Instructions for specific repeatable actions like "shard-doc" or "create-next-story"
- **Checklists** (`bmad-core/checklists/`): Quality assurance checklists for validation and review - **Checklists** (`.bmad-core/checklists/`): Quality assurance checklists for validation and review
- **Data** (`bmad-core/data/`): Core knowledge base and technical preferences - **Data** (`.bmad-core/data/`): Core knowledge base and technical preferences
### Dual Environment Architecture ### Dual Environment Architecture

18
dist/agents/bmad-master.txt vendored
View File

@ -50,7 +50,7 @@ activation-instructions:
- The agent.customization field ALWAYS takes precedence over any conflicting instructions - The agent.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 - 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
- STAY IN CHARACTER! - STAY IN CHARACTER!
- 'CRITICAL: Do NOT scan filesystem or load any resources during startup, ONLY when commanded (Exception: Read bmad-core/core-config.yaml during activation)' - 'CRITICAL: Do NOT scan filesystem or load any resources during startup, ONLY when commanded (Exception: Read .bmad-core/core-config.yaml during activation)'
agent: agent:
name: BMad Master name: BMad Master
id: bmad-master id: bmad-master
@ -8145,24 +8145,24 @@ You are the "Vibe CEO" - thinking like a CEO with unlimited resources and a sing
### System Overview ### System Overview
The BMAD-METHOD™ is built around a modular architecture centered on the `bmad-core` directory, which serves as the brain of the entire system. This design enables the framework to operate effectively in both IDE environments (like Cursor, VS Code) and web-based AI interfaces (like ChatGPT, Gemini). The BMAD-METHOD™ is built around a modular architecture centered on the `.bmad-core` directory, which serves as the brain of the entire system. This design enables the framework to operate effectively in both IDE environments (like Cursor, VS Code) and web-based AI interfaces (like ChatGPT, Gemini).
### Key Architectural Components ### Key Architectural Components
#### 1. Agents (`bmad-core/agents/`) #### 1. Agents (`.bmad-core/agents/`)
- **Purpose**: Each markdown file defines a specialized AI agent for a specific Agile role (PM, Dev, Architect, etc.) - **Purpose**: Each markdown file defines a specialized AI agent for a specific Agile role (PM, Dev, Architect, etc.)
- **Structure**: Contains YAML headers specifying the agent's persona, capabilities, and dependencies - **Structure**: Contains YAML headers specifying the agent's persona, capabilities, and dependencies
- **Dependencies**: Lists of tasks, templates, checklists, and data files the agent can use - **Dependencies**: Lists of tasks, templates, checklists, and data files the agent can use
- **Startup Instructions**: Can load project-specific documentation for immediate context - **Startup Instructions**: Can load project-specific documentation for immediate context
#### 2. Agent Teams (`bmad-core/agent-teams/`) #### 2. Agent Teams (`.bmad-core/agent-teams/`)
- **Purpose**: Define collections of agents bundled together for specific purposes - **Purpose**: Define collections of agents bundled together for specific purposes
- **Examples**: `team-all.yaml` (comprehensive bundle), `team-fullstack.yaml` (full-stack development) - **Examples**: `team-all.yaml` (comprehensive bundle), `team-fullstack.yaml` (full-stack development)
- **Usage**: Creates pre-packaged contexts for web UI environments - **Usage**: Creates pre-packaged contexts for web UI environments
#### 3. Workflows (`bmad-core/workflows/`) #### 3. Workflows (`.bmad-core/workflows/`)
- **Purpose**: YAML files defining prescribed sequences of steps for specific project types - **Purpose**: YAML files defining prescribed sequences of steps for specific project types
- **Types**: Greenfield (new projects) and Brownfield (existing projects) for UI, service, and fullstack development - **Types**: Greenfield (new projects) and Brownfield (existing projects) for UI, service, and fullstack development
@ -8170,10 +8170,10 @@ The BMAD-METHOD™ is built around a modular architecture centered on the `bmad-
#### 4. Reusable Resources #### 4. Reusable Resources
- **Templates** (`bmad-core/templates/`): Markdown templates for PRDs, architecture specs, user stories - **Templates** (`.bmad-core/templates/`): Markdown templates for PRDs, architecture specs, user stories
- **Tasks** (`bmad-core/tasks/`): Instructions for specific repeatable actions like "shard-doc" or "create-next-story" - **Tasks** (`.bmad-core/tasks/`): Instructions for specific repeatable actions like "shard-doc" or "create-next-story"
- **Checklists** (`bmad-core/checklists/`): Quality assurance checklists for validation and review - **Checklists** (`.bmad-core/checklists/`): Quality assurance checklists for validation and review
- **Data** (`bmad-core/data/`): Core knowledge base and technical preferences - **Data** (`.bmad-core/data/`): Core knowledge base and technical preferences
### Dual Environment Architecture ### Dual Environment Architecture

16
dist/agents/bmad-orchestrator.txt vendored
View File

@ -828,24 +828,24 @@ You are the "Vibe CEO" - thinking like a CEO with unlimited resources and a sing
### System Overview ### System Overview
The BMAD-METHOD™ is built around a modular architecture centered on the `bmad-core` directory, which serves as the brain of the entire system. This design enables the framework to operate effectively in both IDE environments (like Cursor, VS Code) and web-based AI interfaces (like ChatGPT, Gemini). The BMAD-METHOD™ is built around a modular architecture centered on the `.bmad-core` directory, which serves as the brain of the entire system. This design enables the framework to operate effectively in both IDE environments (like Cursor, VS Code) and web-based AI interfaces (like ChatGPT, Gemini).
### Key Architectural Components ### Key Architectural Components
#### 1. Agents (`bmad-core/agents/`) #### 1. Agents (`.bmad-core/agents/`)
- **Purpose**: Each markdown file defines a specialized AI agent for a specific Agile role (PM, Dev, Architect, etc.) - **Purpose**: Each markdown file defines a specialized AI agent for a specific Agile role (PM, Dev, Architect, etc.)
- **Structure**: Contains YAML headers specifying the agent's persona, capabilities, and dependencies - **Structure**: Contains YAML headers specifying the agent's persona, capabilities, and dependencies
- **Dependencies**: Lists of tasks, templates, checklists, and data files the agent can use - **Dependencies**: Lists of tasks, templates, checklists, and data files the agent can use
- **Startup Instructions**: Can load project-specific documentation for immediate context - **Startup Instructions**: Can load project-specific documentation for immediate context
#### 2. Agent Teams (`bmad-core/agent-teams/`) #### 2. Agent Teams (`.bmad-core/agent-teams/`)
- **Purpose**: Define collections of agents bundled together for specific purposes - **Purpose**: Define collections of agents bundled together for specific purposes
- **Examples**: `team-all.yaml` (comprehensive bundle), `team-fullstack.yaml` (full-stack development) - **Examples**: `team-all.yaml` (comprehensive bundle), `team-fullstack.yaml` (full-stack development)
- **Usage**: Creates pre-packaged contexts for web UI environments - **Usage**: Creates pre-packaged contexts for web UI environments
#### 3. Workflows (`bmad-core/workflows/`) #### 3. Workflows (`.bmad-core/workflows/`)
- **Purpose**: YAML files defining prescribed sequences of steps for specific project types - **Purpose**: YAML files defining prescribed sequences of steps for specific project types
- **Types**: Greenfield (new projects) and Brownfield (existing projects) for UI, service, and fullstack development - **Types**: Greenfield (new projects) and Brownfield (existing projects) for UI, service, and fullstack development
@ -853,10 +853,10 @@ The BMAD-METHOD™ is built around a modular architecture centered on the `bmad-
#### 4. Reusable Resources #### 4. Reusable Resources
- **Templates** (`bmad-core/templates/`): Markdown templates for PRDs, architecture specs, user stories - **Templates** (`.bmad-core/templates/`): Markdown templates for PRDs, architecture specs, user stories
- **Tasks** (`bmad-core/tasks/`): Instructions for specific repeatable actions like "shard-doc" or "create-next-story" - **Tasks** (`.bmad-core/tasks/`): Instructions for specific repeatable actions like "shard-doc" or "create-next-story"
- **Checklists** (`bmad-core/checklists/`): Quality assurance checklists for validation and review - **Checklists** (`.bmad-core/checklists/`): Quality assurance checklists for validation and review
- **Data** (`bmad-core/data/`): Core knowledge base and technical preferences - **Data** (`.bmad-core/data/`): Core knowledge base and technical preferences
### Dual Environment Architecture ### Dual Environment Architecture

4
dist/agents/dev.txt vendored
View File

@ -353,11 +353,11 @@ To comprehensively validate a story draft before implementation begins, ensuring
- **Story file**: The drafted story to validate (provided by user or discovered in `devStoryLocation`) - **Story file**: The drafted story to validate (provided by user or discovered in `devStoryLocation`)
- **Parent epic**: The epic containing this story's requirements - **Parent epic**: The epic containing this story's requirements
- **Architecture documents**: Based on configuration (sharded or monolithic) - **Architecture documents**: Based on configuration (sharded or monolithic)
- **Story template**: `bmad-core/templates/story-tmpl.md` for completeness validation - **Story template**: `.bmad-core/templates/story-tmpl.md` for completeness validation
### 1. Template Completeness Validation ### 1. Template Completeness Validation
- Load `bmad-core/templates/story-tmpl.md` and extract all section headings from the template - Load `.bmad-core/templates/story-tmpl.md` and extract all section headings from the template
- **Missing sections check**: Compare story sections against template sections to verify all required sections are present - **Missing sections check**: Compare story sections against template sections to verify all required sections are present
- **Placeholder validation**: Ensure no template placeholders remain unfilled (e.g., `{{EpicNum}}`, `{{role}}`, `_TBD_`) - **Placeholder validation**: Ensure no template placeholders remain unfilled (e.g., `{{EpicNum}}`, `{{role}}`, `_TBD_`)
- **Agent section verification**: Confirm all sections from template exist for future agent use - **Agent section verification**: Confirm all sections from template exist for future agent use

4
dist/agents/po.txt vendored
View File

@ -470,11 +470,11 @@ To comprehensively validate a story draft before implementation begins, ensuring
- **Story file**: The drafted story to validate (provided by user or discovered in `devStoryLocation`) - **Story file**: The drafted story to validate (provided by user or discovered in `devStoryLocation`)
- **Parent epic**: The epic containing this story's requirements - **Parent epic**: The epic containing this story's requirements
- **Architecture documents**: Based on configuration (sharded or monolithic) - **Architecture documents**: Based on configuration (sharded or monolithic)
- **Story template**: `bmad-core/templates/story-tmpl.md` for completeness validation - **Story template**: `.bmad-core/templates/story-tmpl.md` for completeness validation
### 1. Template Completeness Validation ### 1. Template Completeness Validation
- Load `bmad-core/templates/story-tmpl.md` and extract all section headings from the template - Load `.bmad-core/templates/story-tmpl.md` and extract all section headings from the template
- **Missing sections check**: Compare story sections against template sections to verify all required sections are present - **Missing sections check**: Compare story sections against template sections to verify all required sections are present
- **Placeholder validation**: Ensure no template placeholders remain unfilled (e.g., `{{EpicNum}}`, `{{role}}`, `_TBD_`) - **Placeholder validation**: Ensure no template placeholders remain unfilled (e.g., `{{EpicNum}}`, `{{role}}`, `_TBD_`)
- **Agent section verification**: Confirm all sections from template exist for future agent use - **Agent section verification**: Confirm all sections from template exist for future agent use

2
dist/expansion-packs/bmad-2d-unity-game-dev/agents/game-architect.txt vendored
View File

@ -3698,7 +3698,7 @@ Use the `shard-doc` task or `@kayvan/markdown-tree-parser` tool for automatic ga
| `game-sm` | Game Scrum Master | Game story creation, sprint planning | Game project management, workflow | | `game-sm` | Game Scrum Master | Game story creation, sprint planning | Game project management, workflow |
| `game-architect` | Game Architect | Unity system design, technical architecture | Complex Unity systems, performance planning | | `game-architect` | Game Architect | Unity system design, technical architecture | Complex Unity systems, performance planning |
**Note**: For QA and other roles, use the core BMad agents (e.g., `@qa` from bmad-core). **Note**: For QA and other roles, use the core BMad agents (e.g., `@qa` from .bmad-core).
### Game Agent Interaction Commands ### Game Agent Interaction Commands

2
dist/expansion-packs/bmad-2d-unity-game-dev/agents/game-designer.txt vendored
View File

@ -3385,7 +3385,7 @@ Use the `shard-doc` task or `@kayvan/markdown-tree-parser` tool for automatic ga
| `game-sm` | Game Scrum Master | Game story creation, sprint planning | Game project management, workflow | | `game-sm` | Game Scrum Master | Game story creation, sprint planning | Game project management, workflow |
| `game-architect` | Game Architect | Unity system design, technical architecture | Complex Unity systems, performance planning | | `game-architect` | Game Architect | Unity system design, technical architecture | Complex Unity systems, performance planning |
**Note**: For QA and other roles, use the core BMad agents (e.g., `@qa` from bmad-core). **Note**: For QA and other roles, use the core BMad agents (e.g., `@qa` from .bmad-core).
### Game Agent Interaction Commands ### Game Agent Interaction Commands

4
dist/expansion-packs/bmad-2d-unity-game-dev/agents/game-developer.txt vendored
View File

@ -205,11 +205,11 @@ To comprehensively validate a story draft before implementation begins, ensuring
- **Story file**: The drafted story to validate (provided by user or discovered in `devStoryLocation`) - **Story file**: The drafted story to validate (provided by user or discovered in `devStoryLocation`)
- **Parent epic**: The epic containing this story's requirements - **Parent epic**: The epic containing this story's requirements
- **Architecture documents**: Based on configuration (sharded or monolithic) - **Architecture documents**: Based on configuration (sharded or monolithic)
- **Story template**: `bmad-core/templates/story-tmpl.md` for completeness validation - **Story template**: `.bmad-core/templates/story-tmpl.md` for completeness validation
### 1. Template Completeness Validation ### 1. Template Completeness Validation
- Load `bmad-core/templates/story-tmpl.md` and extract all section headings from the template - Load `.bmad-core/templates/story-tmpl.md` and extract all section headings from the template
- **Missing sections check**: Compare story sections against template sections to verify all required sections are present - **Missing sections check**: Compare story sections against template sections to verify all required sections are present
- **Placeholder validation**: Ensure no template placeholders remain unfilled (e.g., `{{EpicNum}}`, `{{role}}`, `_TBD_`) - **Placeholder validation**: Ensure no template placeholders remain unfilled (e.g., `{{EpicNum}}`, `{{role}}`, `_TBD_`)
- **Agent section verification**: Confirm all sections from template exist for future agent use - **Agent section verification**: Confirm all sections from template exist for future agent use

8
dist/expansion-packs/bmad-2d-unity-game-dev/teams/unity-2d-game-team.txt vendored
View File

@ -926,7 +926,7 @@ Use the `shard-doc` task or `@kayvan/markdown-tree-parser` tool for automatic ga
| `game-sm` | Game Scrum Master | Game story creation, sprint planning | Game project management, workflow | | `game-sm` | Game Scrum Master | Game story creation, sprint planning | Game project management, workflow |
| `game-architect` | Game Architect | Unity system design, technical architecture | Complex Unity systems, performance planning | | `game-architect` | Game Architect | Unity system design, technical architecture | Complex Unity systems, performance planning |
**Note**: For QA and other roles, use the core BMad agents (e.g., `@qa` from bmad-core). **Note**: For QA and other roles, use the core BMad agents (e.g., `@qa` from .bmad-core).
### Game Agent Interaction Commands ### Game Agent Interaction Commands
@ -7910,11 +7910,11 @@ To comprehensively validate a story draft before implementation begins, ensuring
- **Story file**: The drafted story to validate (provided by user or discovered in `devStoryLocation`) - **Story file**: The drafted story to validate (provided by user or discovered in `devStoryLocation`)
- **Parent epic**: The epic containing this story's requirements - **Parent epic**: The epic containing this story's requirements
- **Architecture documents**: Based on configuration (sharded or monolithic) - **Architecture documents**: Based on configuration (sharded or monolithic)
- **Story template**: `bmad-core/templates/story-tmpl.md` for completeness validation - **Story template**: `.bmad-core/templates/story-tmpl.md` for completeness validation
### 1. Template Completeness Validation ### 1. Template Completeness Validation
- Load `bmad-core/templates/story-tmpl.md` and extract all section headings from the template - Load `.bmad-core/templates/story-tmpl.md` and extract all section headings from the template
- **Missing sections check**: Compare story sections against template sections to verify all required sections are present - **Missing sections check**: Compare story sections against template sections to verify all required sections are present
- **Placeholder validation**: Ensure no template placeholders remain unfilled (e.g., `{{EpicNum}}`, `{{role}}`, `_TBD_`) - **Placeholder validation**: Ensure no template placeholders remain unfilled (e.g., `{{EpicNum}}`, `{{role}}`, `_TBD_`)
- **Agent section verification**: Confirm all sections from template exist for future agent use - **Agent section verification**: Confirm all sections from template exist for future agent use
@ -14504,7 +14504,7 @@ Use the `shard-doc` task or `@kayvan/markdown-tree-parser` tool for automatic ga
| `game-sm` | Game Scrum Master | Game story creation, sprint planning | Game project management, workflow | | `game-sm` | Game Scrum Master | Game story creation, sprint planning | Game project management, workflow |
| `game-architect` | Game Architect | Unity system design, technical architecture | Complex Unity systems, performance planning | | `game-architect` | Game Architect | Unity system design, technical architecture | Complex Unity systems, performance planning |
**Note**: For QA and other roles, use the core BMad agents (e.g., `@qa` from bmad-core). **Note**: For QA and other roles, use the core BMad agents (e.g., `@qa` from .bmad-core).
### Game Agent Interaction Commands ### Game Agent Interaction Commands

20
dist/teams/team-all.txt vendored
View File

@ -1315,24 +1315,24 @@ You are the "Vibe CEO" - thinking like a CEO with unlimited resources and a sing
### System Overview ### System Overview
The BMAD-METHOD™ is built around a modular architecture centered on the `bmad-core` directory, which serves as the brain of the entire system. This design enables the framework to operate effectively in both IDE environments (like Cursor, VS Code) and web-based AI interfaces (like ChatGPT, Gemini). The BMAD-METHOD™ is built around a modular architecture centered on the `.bmad-core` directory, which serves as the brain of the entire system. This design enables the framework to operate effectively in both IDE environments (like Cursor, VS Code) and web-based AI interfaces (like ChatGPT, Gemini).
### Key Architectural Components ### Key Architectural Components
#### 1. Agents (`bmad-core/agents/`) #### 1. Agents (`.bmad-core/agents/`)
- **Purpose**: Each markdown file defines a specialized AI agent for a specific Agile role (PM, Dev, Architect, etc.) - **Purpose**: Each markdown file defines a specialized AI agent for a specific Agile role (PM, Dev, Architect, etc.)
- **Structure**: Contains YAML headers specifying the agent's persona, capabilities, and dependencies - **Structure**: Contains YAML headers specifying the agent's persona, capabilities, and dependencies
- **Dependencies**: Lists of tasks, templates, checklists, and data files the agent can use - **Dependencies**: Lists of tasks, templates, checklists, and data files the agent can use
- **Startup Instructions**: Can load project-specific documentation for immediate context - **Startup Instructions**: Can load project-specific documentation for immediate context
#### 2. Agent Teams (`bmad-core/agent-teams/`) #### 2. Agent Teams (`.bmad-core/agent-teams/`)
- **Purpose**: Define collections of agents bundled together for specific purposes - **Purpose**: Define collections of agents bundled together for specific purposes
- **Examples**: `team-all.yaml` (comprehensive bundle), `team-fullstack.yaml` (full-stack development) - **Examples**: `team-all.yaml` (comprehensive bundle), `team-fullstack.yaml` (full-stack development)
- **Usage**: Creates pre-packaged contexts for web UI environments - **Usage**: Creates pre-packaged contexts for web UI environments
#### 3. Workflows (`bmad-core/workflows/`) #### 3. Workflows (`.bmad-core/workflows/`)
- **Purpose**: YAML files defining prescribed sequences of steps for specific project types - **Purpose**: YAML files defining prescribed sequences of steps for specific project types
- **Types**: Greenfield (new projects) and Brownfield (existing projects) for UI, service, and fullstack development - **Types**: Greenfield (new projects) and Brownfield (existing projects) for UI, service, and fullstack development
@ -1340,10 +1340,10 @@ The BMAD-METHOD™ is built around a modular architecture centered on the `bmad-
#### 4. Reusable Resources #### 4. Reusable Resources
- **Templates** (`bmad-core/templates/`): Markdown templates for PRDs, architecture specs, user stories - **Templates** (`.bmad-core/templates/`): Markdown templates for PRDs, architecture specs, user stories
- **Tasks** (`bmad-core/tasks/`): Instructions for specific repeatable actions like "shard-doc" or "create-next-story" - **Tasks** (`.bmad-core/tasks/`): Instructions for specific repeatable actions like "shard-doc" or "create-next-story"
- **Checklists** (`bmad-core/checklists/`): Quality assurance checklists for validation and review - **Checklists** (`.bmad-core/checklists/`): Quality assurance checklists for validation and review
- **Data** (`bmad-core/data/`): Core knowledge base and technical preferences - **Data** (`.bmad-core/data/`): Core knowledge base and technical preferences
### Dual Environment Architecture ### Dual Environment Architecture
@ -6651,11 +6651,11 @@ To comprehensively validate a story draft before implementation begins, ensuring
- **Story file**: The drafted story to validate (provided by user or discovered in `devStoryLocation`) - **Story file**: The drafted story to validate (provided by user or discovered in `devStoryLocation`)
- **Parent epic**: The epic containing this story's requirements - **Parent epic**: The epic containing this story's requirements
- **Architecture documents**: Based on configuration (sharded or monolithic) - **Architecture documents**: Based on configuration (sharded or monolithic)
- **Story template**: `bmad-core/templates/story-tmpl.md` for completeness validation - **Story template**: `.bmad-core/templates/story-tmpl.md` for completeness validation
### 1. Template Completeness Validation ### 1. Template Completeness Validation
- Load `bmad-core/templates/story-tmpl.md` and extract all section headings from the template - Load `.bmad-core/templates/story-tmpl.md` and extract all section headings from the template
- **Missing sections check**: Compare story sections against template sections to verify all required sections are present - **Missing sections check**: Compare story sections against template sections to verify all required sections are present
- **Placeholder validation**: Ensure no template placeholders remain unfilled (e.g., `{{EpicNum}}`, `{{role}}`, `_TBD_`) - **Placeholder validation**: Ensure no template placeholders remain unfilled (e.g., `{{EpicNum}}`, `{{role}}`, `_TBD_`)
- **Agent section verification**: Confirm all sections from template exist for future agent use - **Agent section verification**: Confirm all sections from template exist for future agent use

20
dist/teams/team-fullstack.txt vendored
View File

@ -1151,24 +1151,24 @@ You are the "Vibe CEO" - thinking like a CEO with unlimited resources and a sing
### System Overview ### System Overview
The BMAD-METHOD™ is built around a modular architecture centered on the `bmad-core` directory, which serves as the brain of the entire system. This design enables the framework to operate effectively in both IDE environments (like Cursor, VS Code) and web-based AI interfaces (like ChatGPT, Gemini). The BMAD-METHOD™ is built around a modular architecture centered on the `.bmad-core` directory, which serves as the brain of the entire system. This design enables the framework to operate effectively in both IDE environments (like Cursor, VS Code) and web-based AI interfaces (like ChatGPT, Gemini).
### Key Architectural Components ### Key Architectural Components
#### 1. Agents (`bmad-core/agents/`) #### 1. Agents (`.bmad-core/agents/`)
- **Purpose**: Each markdown file defines a specialized AI agent for a specific Agile role (PM, Dev, Architect, etc.) - **Purpose**: Each markdown file defines a specialized AI agent for a specific Agile role (PM, Dev, Architect, etc.)
- **Structure**: Contains YAML headers specifying the agent's persona, capabilities, and dependencies - **Structure**: Contains YAML headers specifying the agent's persona, capabilities, and dependencies
- **Dependencies**: Lists of tasks, templates, checklists, and data files the agent can use - **Dependencies**: Lists of tasks, templates, checklists, and data files the agent can use
- **Startup Instructions**: Can load project-specific documentation for immediate context - **Startup Instructions**: Can load project-specific documentation for immediate context
#### 2. Agent Teams (`bmad-core/agent-teams/`) #### 2. Agent Teams (`.bmad-core/agent-teams/`)
- **Purpose**: Define collections of agents bundled together for specific purposes - **Purpose**: Define collections of agents bundled together for specific purposes
- **Examples**: `team-all.yaml` (comprehensive bundle), `team-fullstack.yaml` (full-stack development) - **Examples**: `team-all.yaml` (comprehensive bundle), `team-fullstack.yaml` (full-stack development)
- **Usage**: Creates pre-packaged contexts for web UI environments - **Usage**: Creates pre-packaged contexts for web UI environments
#### 3. Workflows (`bmad-core/workflows/`) #### 3. Workflows (`.bmad-core/workflows/`)
- **Purpose**: YAML files defining prescribed sequences of steps for specific project types - **Purpose**: YAML files defining prescribed sequences of steps for specific project types
- **Types**: Greenfield (new projects) and Brownfield (existing projects) for UI, service, and fullstack development - **Types**: Greenfield (new projects) and Brownfield (existing projects) for UI, service, and fullstack development
@ -1176,10 +1176,10 @@ The BMAD-METHOD™ is built around a modular architecture centered on the `bmad-
#### 4. Reusable Resources #### 4. Reusable Resources
- **Templates** (`bmad-core/templates/`): Markdown templates for PRDs, architecture specs, user stories - **Templates** (`.bmad-core/templates/`): Markdown templates for PRDs, architecture specs, user stories
- **Tasks** (`bmad-core/tasks/`): Instructions for specific repeatable actions like "shard-doc" or "create-next-story" - **Tasks** (`.bmad-core/tasks/`): Instructions for specific repeatable actions like "shard-doc" or "create-next-story"
- **Checklists** (`bmad-core/checklists/`): Quality assurance checklists for validation and review - **Checklists** (`.bmad-core/checklists/`): Quality assurance checklists for validation and review
- **Data** (`bmad-core/data/`): Core knowledge base and technical preferences - **Data** (`.bmad-core/data/`): Core knowledge base and technical preferences
### Dual Environment Architecture ### Dual Environment Architecture
@ -8371,11 +8371,11 @@ To comprehensively validate a story draft before implementation begins, ensuring
- **Story file**: The drafted story to validate (provided by user or discovered in `devStoryLocation`) - **Story file**: The drafted story to validate (provided by user or discovered in `devStoryLocation`)
- **Parent epic**: The epic containing this story's requirements - **Parent epic**: The epic containing this story's requirements
- **Architecture documents**: Based on configuration (sharded or monolithic) - **Architecture documents**: Based on configuration (sharded or monolithic)
- **Story template**: `bmad-core/templates/story-tmpl.md` for completeness validation - **Story template**: `.bmad-core/templates/story-tmpl.md` for completeness validation
### 1. Template Completeness Validation ### 1. Template Completeness Validation
- Load `bmad-core/templates/story-tmpl.md` and extract all section headings from the template - Load `.bmad-core/templates/story-tmpl.md` and extract all section headings from the template
- **Missing sections check**: Compare story sections against template sections to verify all required sections are present - **Missing sections check**: Compare story sections against template sections to verify all required sections are present
- **Placeholder validation**: Ensure no template placeholders remain unfilled (e.g., `{{EpicNum}}`, `{{role}}`, `_TBD_`) - **Placeholder validation**: Ensure no template placeholders remain unfilled (e.g., `{{EpicNum}}`, `{{role}}`, `_TBD_`)
- **Agent section verification**: Confirm all sections from template exist for future agent use - **Agent section verification**: Confirm all sections from template exist for future agent use

20
dist/teams/team-ide-minimal.txt vendored
View File

@ -1069,24 +1069,24 @@ You are the "Vibe CEO" - thinking like a CEO with unlimited resources and a sing
### System Overview ### System Overview
The BMAD-METHOD™ is built around a modular architecture centered on the `bmad-core` directory, which serves as the brain of the entire system. This design enables the framework to operate effectively in both IDE environments (like Cursor, VS Code) and web-based AI interfaces (like ChatGPT, Gemini). The BMAD-METHOD™ is built around a modular architecture centered on the `.bmad-core` directory, which serves as the brain of the entire system. This design enables the framework to operate effectively in both IDE environments (like Cursor, VS Code) and web-based AI interfaces (like ChatGPT, Gemini).
### Key Architectural Components ### Key Architectural Components
#### 1. Agents (`bmad-core/agents/`) #### 1. Agents (`.bmad-core/agents/`)
- **Purpose**: Each markdown file defines a specialized AI agent for a specific Agile role (PM, Dev, Architect, etc.) - **Purpose**: Each markdown file defines a specialized AI agent for a specific Agile role (PM, Dev, Architect, etc.)
- **Structure**: Contains YAML headers specifying the agent's persona, capabilities, and dependencies - **Structure**: Contains YAML headers specifying the agent's persona, capabilities, and dependencies
- **Dependencies**: Lists of tasks, templates, checklists, and data files the agent can use - **Dependencies**: Lists of tasks, templates, checklists, and data files the agent can use
- **Startup Instructions**: Can load project-specific documentation for immediate context - **Startup Instructions**: Can load project-specific documentation for immediate context
#### 2. Agent Teams (`bmad-core/agent-teams/`) #### 2. Agent Teams (`.bmad-core/agent-teams/`)
- **Purpose**: Define collections of agents bundled together for specific purposes - **Purpose**: Define collections of agents bundled together for specific purposes
- **Examples**: `team-all.yaml` (comprehensive bundle), `team-fullstack.yaml` (full-stack development) - **Examples**: `team-all.yaml` (comprehensive bundle), `team-fullstack.yaml` (full-stack development)
- **Usage**: Creates pre-packaged contexts for web UI environments - **Usage**: Creates pre-packaged contexts for web UI environments
#### 3. Workflows (`bmad-core/workflows/`) #### 3. Workflows (`.bmad-core/workflows/`)
- **Purpose**: YAML files defining prescribed sequences of steps for specific project types - **Purpose**: YAML files defining prescribed sequences of steps for specific project types
- **Types**: Greenfield (new projects) and Brownfield (existing projects) for UI, service, and fullstack development - **Types**: Greenfield (new projects) and Brownfield (existing projects) for UI, service, and fullstack development
@ -1094,10 +1094,10 @@ The BMAD-METHOD™ is built around a modular architecture centered on the `bmad-
#### 4. Reusable Resources #### 4. Reusable Resources
- **Templates** (`bmad-core/templates/`): Markdown templates for PRDs, architecture specs, user stories - **Templates** (`.bmad-core/templates/`): Markdown templates for PRDs, architecture specs, user stories
- **Tasks** (`bmad-core/tasks/`): Instructions for specific repeatable actions like "shard-doc" or "create-next-story" - **Tasks** (`.bmad-core/tasks/`): Instructions for specific repeatable actions like "shard-doc" or "create-next-story"
- **Checklists** (`bmad-core/checklists/`): Quality assurance checklists for validation and review - **Checklists** (`.bmad-core/checklists/`): Quality assurance checklists for validation and review
- **Data** (`bmad-core/data/`): Core knowledge base and technical preferences - **Data** (`.bmad-core/data/`): Core knowledge base and technical preferences
### Dual Environment Architecture ### Dual Environment Architecture
@ -2125,11 +2125,11 @@ To comprehensively validate a story draft before implementation begins, ensuring
- **Story file**: The drafted story to validate (provided by user or discovered in `devStoryLocation`) - **Story file**: The drafted story to validate (provided by user or discovered in `devStoryLocation`)
- **Parent epic**: The epic containing this story's requirements - **Parent epic**: The epic containing this story's requirements
- **Architecture documents**: Based on configuration (sharded or monolithic) - **Architecture documents**: Based on configuration (sharded or monolithic)
- **Story template**: `bmad-core/templates/story-tmpl.md` for completeness validation - **Story template**: `.bmad-core/templates/story-tmpl.md` for completeness validation
### 1. Template Completeness Validation ### 1. Template Completeness Validation
- Load `bmad-core/templates/story-tmpl.md` and extract all section headings from the template - Load `.bmad-core/templates/story-tmpl.md` and extract all section headings from the template
- **Missing sections check**: Compare story sections against template sections to verify all required sections are present - **Missing sections check**: Compare story sections against template sections to verify all required sections are present
- **Placeholder validation**: Ensure no template placeholders remain unfilled (e.g., `{{EpicNum}}`, `{{role}}`, `_TBD_`) - **Placeholder validation**: Ensure no template placeholders remain unfilled (e.g., `{{EpicNum}}`, `{{role}}`, `_TBD_`)
- **Agent section verification**: Confirm all sections from template exist for future agent use - **Agent section verification**: Confirm all sections from template exist for future agent use

20
dist/teams/team-no-ui.txt vendored
View File

@ -1097,24 +1097,24 @@ You are the "Vibe CEO" - thinking like a CEO with unlimited resources and a sing
### System Overview ### System Overview
The BMAD-METHOD™ is built around a modular architecture centered on the `bmad-core` directory, which serves as the brain of the entire system. This design enables the framework to operate effectively in both IDE environments (like Cursor, VS Code) and web-based AI interfaces (like ChatGPT, Gemini). The BMAD-METHOD™ is built around a modular architecture centered on the `.bmad-core` directory, which serves as the brain of the entire system. This design enables the framework to operate effectively in both IDE environments (like Cursor, VS Code) and web-based AI interfaces (like ChatGPT, Gemini).
### Key Architectural Components ### Key Architectural Components
#### 1. Agents (`bmad-core/agents/`) #### 1. Agents (`.bmad-core/agents/`)
- **Purpose**: Each markdown file defines a specialized AI agent for a specific Agile role (PM, Dev, Architect, etc.) - **Purpose**: Each markdown file defines a specialized AI agent for a specific Agile role (PM, Dev, Architect, etc.)
- **Structure**: Contains YAML headers specifying the agent's persona, capabilities, and dependencies - **Structure**: Contains YAML headers specifying the agent's persona, capabilities, and dependencies
- **Dependencies**: Lists of tasks, templates, checklists, and data files the agent can use - **Dependencies**: Lists of tasks, templates, checklists, and data files the agent can use
- **Startup Instructions**: Can load project-specific documentation for immediate context - **Startup Instructions**: Can load project-specific documentation for immediate context
#### 2. Agent Teams (`bmad-core/agent-teams/`) #### 2. Agent Teams (`.bmad-core/agent-teams/`)
- **Purpose**: Define collections of agents bundled together for specific purposes - **Purpose**: Define collections of agents bundled together for specific purposes
- **Examples**: `team-all.yaml` (comprehensive bundle), `team-fullstack.yaml` (full-stack development) - **Examples**: `team-all.yaml` (comprehensive bundle), `team-fullstack.yaml` (full-stack development)
- **Usage**: Creates pre-packaged contexts for web UI environments - **Usage**: Creates pre-packaged contexts for web UI environments
#### 3. Workflows (`bmad-core/workflows/`) #### 3. Workflows (`.bmad-core/workflows/`)
- **Purpose**: YAML files defining prescribed sequences of steps for specific project types - **Purpose**: YAML files defining prescribed sequences of steps for specific project types
- **Types**: Greenfield (new projects) and Brownfield (existing projects) for UI, service, and fullstack development - **Types**: Greenfield (new projects) and Brownfield (existing projects) for UI, service, and fullstack development
@ -1122,10 +1122,10 @@ The BMAD-METHOD™ is built around a modular architecture centered on the `bmad-
#### 4. Reusable Resources #### 4. Reusable Resources
- **Templates** (`bmad-core/templates/`): Markdown templates for PRDs, architecture specs, user stories - **Templates** (`.bmad-core/templates/`): Markdown templates for PRDs, architecture specs, user stories
- **Tasks** (`bmad-core/tasks/`): Instructions for specific repeatable actions like "shard-doc" or "create-next-story" - **Tasks** (`.bmad-core/tasks/`): Instructions for specific repeatable actions like "shard-doc" or "create-next-story"
- **Checklists** (`bmad-core/checklists/`): Quality assurance checklists for validation and review - **Checklists** (`.bmad-core/checklists/`): Quality assurance checklists for validation and review
- **Data** (`bmad-core/data/`): Core knowledge base and technical preferences - **Data** (`.bmad-core/data/`): Core knowledge base and technical preferences
### Dual Environment Architecture ### Dual Environment Architecture
@ -7909,11 +7909,11 @@ To comprehensively validate a story draft before implementation begins, ensuring
- **Story file**: The drafted story to validate (provided by user or discovered in `devStoryLocation`) - **Story file**: The drafted story to validate (provided by user or discovered in `devStoryLocation`)
- **Parent epic**: The epic containing this story's requirements - **Parent epic**: The epic containing this story's requirements
- **Architecture documents**: Based on configuration (sharded or monolithic) - **Architecture documents**: Based on configuration (sharded or monolithic)
- **Story template**: `bmad-core/templates/story-tmpl.md` for completeness validation - **Story template**: `.bmad-core/templates/story-tmpl.md` for completeness validation
### 1. Template Completeness Validation ### 1. Template Completeness Validation
- Load `bmad-core/templates/story-tmpl.md` and extract all section headings from the template - Load `.bmad-core/templates/story-tmpl.md` and extract all section headings from the template
- **Missing sections check**: Compare story sections against template sections to verify all required sections are present - **Missing sections check**: Compare story sections against template sections to verify all required sections are present
- **Placeholder validation**: Ensure no template placeholders remain unfilled (e.g., `{{EpicNum}}`, `{{role}}`, `_TBD_`) - **Placeholder validation**: Ensure no template placeholders remain unfilled (e.g., `{{EpicNum}}`, `{{role}}`, `_TBD_`)
- **Agent section verification**: Confirm all sections from template exist for future agent use - **Agent section verification**: Confirm all sections from template exist for future agent use

20
docs/core-architecture.md
View File

@ -12,7 +12,7 @@ The systems core module facilitates a full development lifecycle tailored to the
## 2. System Architecture Diagram ## 2. System Architecture Diagram
The entire BMad-Method ecosystem is designed around the installed `bmad-core` directory, which acts as the brain of the operation. The `tools` directory provides the means to process and package this brain for different environments. The entire BMad-Method ecosystem is designed around the installed `.bmad-core` directory, which acts as the brain of the operation. The `tools` directory provides the means to process and package this brain for different environments.
```mermaid ```mermaid
graph TD graph TD
@ -61,9 +61,9 @@ graph TD
## 3. Core Components ## 3. Core Components
The `bmad-core` directory contains all the definitions and resources that give the agents their capabilities. The `.bmad-core` directory contains all the definitions and resources that give the agents their capabilities.
### 3.1. Agents (`bmad-core/agents/`) ### 3.1. Agents (`.bmad-core/agents/`)
- **Purpose**: These are the foundational building blocks of the system. Each markdown file (e.g., `bmad-master.md`, `pm.md`, `dev.md`) defines the persona, capabilities, and dependencies of a single AI agent. - **Purpose**: These are the foundational building blocks of the system. Each markdown file (e.g., `bmad-master.md`, `pm.md`, `dev.md`) defines the persona, capabilities, and dependencies of a single AI agent.
- **Structure**: An agent file contains a YAML header that specifies its role, persona, dependencies, and startup instructions. These dependencies are lists of tasks, templates, checklists, and data files that the agent is allowed to use. - **Structure**: An agent file contains a YAML header that specifies its role, persona, dependencies, and startup instructions. These dependencies are lists of tasks, templates, checklists, and data files that the agent is allowed to use.
@ -71,12 +71,12 @@ The `bmad-core` directory contains all the definitions and resources that give t
- **Document Integration**: Agents can reference and load documents from the project's `docs/` folder as part of tasks, workflows, or startup sequences. Users can also drag documents directly into chat interfaces to provide additional context. - **Document Integration**: Agents can reference and load documents from the project's `docs/` folder as part of tasks, workflows, or startup sequences. Users can also drag documents directly into chat interfaces to provide additional context.
- **Example**: The `bmad-master` agent lists its dependencies, which tells the build tool which files to include in a web bundle and informs the agent of its own capabilities. - **Example**: The `bmad-master` agent lists its dependencies, which tells the build tool which files to include in a web bundle and informs the agent of its own capabilities.
### 3.2. Agent Teams (`bmad-core/agent-teams/`) ### 3.2. Agent Teams (`.bmad-core/agent-teams/`)
- **Purpose**: Team files (e.g., `team-all.yaml`) define collections of agents and workflows that are bundled together for a specific purpose, like "full-stack development" or "backend-only". This creates a larger, pre-packaged context for web UI environments. - **Purpose**: Team files (e.g., `team-all.yaml`) define collections of agents and workflows that are bundled together for a specific purpose, like "full-stack development" or "backend-only". This creates a larger, pre-packaged context for web UI environments.
- **Structure**: A team file lists the agents to include. It can use wildcards, such as `"*"` to include all agents. This allows for the creation of comprehensive bundles like `team-all`. - **Structure**: A team file lists the agents to include. It can use wildcards, such as `"*"` to include all agents. This allows for the creation of comprehensive bundles like `team-all`.
### 3.3. Workflows (`bmad-core/workflows/`) ### 3.3. Workflows (`.bmad-core/workflows/`)
- **Purpose**: Workflows are YAML files (e.g., `greenfield-fullstack.yaml`) that define a prescribed sequence of steps and agent interactions for a specific project type. They act as a strategic guide for the user and the `bmad-orchestrator` agent. - **Purpose**: Workflows are YAML files (e.g., `greenfield-fullstack.yaml`) that define a prescribed sequence of steps and agent interactions for a specific project type. They act as a strategic guide for the user and the `bmad-orchestrator` agent.
- **Structure**: A workflow defines sequences for both complex and simple projects, lists the agents involved at each step, the artifacts they create, and the conditions for moving from one step to the next. It often includes a Mermaid diagram for visualization. - **Structure**: A workflow defines sequences for both complex and simple projects, lists the agents involved at each step, the artifacts they create, and the conditions for moving from one step to the next. It often includes a Mermaid diagram for visualization.
@ -95,17 +95,17 @@ A key architectural principle of BMad is that templates are self-contained and i
The BMad framework employs a sophisticated template processing system orchestrated by three key components: The BMad framework employs a sophisticated template processing system orchestrated by three key components:
- **`template-format.md`** (`bmad-core/utils/`): Defines the foundational markup language used throughout all BMad templates. This specification establishes syntax rules for variable substitution (`{{placeholders}}`), AI-only processing directives (`[[LLM: instructions]]`), and conditional logic blocks. Templates follow this format to ensure consistent processing across the system. - **`template-format.md`** (`.bmad-core/utils/`): Defines the foundational markup language used throughout all BMad templates. This specification establishes syntax rules for variable substitution (`{{placeholders}}`), AI-only processing directives (`[[LLM: instructions]]`), and conditional logic blocks. Templates follow this format to ensure consistent processing across the system.
- **`create-doc.md`** (`bmad-core/tasks/`): Acts as the orchestration engine that manages the entire document generation workflow. This task coordinates template selection, manages user interaction modes (incremental vs. rapid generation), enforces template-format processing rules, and handles validation. It serves as the primary interface between users and the template system. - **`create-doc.md`** (`.bmad-core/tasks/`): Acts as the orchestration engine that manages the entire document generation workflow. This task coordinates template selection, manages user interaction modes (incremental vs. rapid generation), enforces template-format processing rules, and handles validation. It serves as the primary interface between users and the template system.
- **`advanced-elicitation.md`** (`bmad-core/tasks/`): Provides an interactive refinement layer that can be embedded within templates through `[[LLM: instructions]]` blocks. This component offers 10 structured brainstorming actions, section-by-section review capabilities, and iterative improvement workflows to enhance content quality. - **`advanced-elicitation.md`** (`.bmad-core/tasks/`): Provides an interactive refinement layer that can be embedded within templates through `[[LLM: instructions]]` blocks. This component offers 10 structured brainstorming actions, section-by-section review capabilities, and iterative improvement workflows to enhance content quality.
The system maintains a clean separation of concerns: template markup is processed internally by AI agents but never exposed to users, while providing sophisticated AI processing capabilities through embedded intelligence within the templates themselves. The system maintains a clean separation of concerns: template markup is processed internally by AI agents but never exposed to users, while providing sophisticated AI processing capabilities through embedded intelligence within the templates themselves.
#### 3.4.2. Technical Preferences System #### 3.4.2. Technical Preferences System
BMad includes a personalization layer through the `technical-preferences.md` file in `bmad-core/data/`. This file serves as a persistent technical profile that influences agent behavior across all projects. BMad includes a personalization layer through the `technical-preferences.md` file in `.bmad-core/data/`. This file serves as a persistent technical profile that influences agent behavior across all projects.
**Purpose and Benefits:** **Purpose and Benefits:**
@ -142,7 +142,7 @@ The framework is designed for two primary environments: local IDEs and web-based
### 4.2. Environment-Specific Usage ### 4.2. Environment-Specific Usage
- **For IDEs**: Users interact with the agents directly via their markdown files in `bmad-core/agents/`. The IDE integration (for Cursor, Claude Code, etc.) knows how to call these agents. - **For IDEs**: Users interact with the agents directly via their markdown files in `.bmad-core/agents/`. The IDE integration (for Cursor, Claude Code, etc.) knows how to call these agents.
- **For Web UIs**: Users upload a pre-built bundle from `dist`. This single file provides the AI with the context of the entire team and all their required tools and knowledge. - **For Web UIs**: Users upload a pre-built bundle from `dist`. This single file provides the AI with the context of the entire team and all their required tools and knowledge.
## 5. BMad Workflows ## 5. BMad Workflows

2
expansion-packs/bmad-2d-unity-game-dev/data/bmad-kb.md
View File

@ -448,7 +448,7 @@ Use the `shard-doc` task or `@kayvan/markdown-tree-parser` tool for automatic ga
| `game-sm` | Game Scrum Master | Game story creation, sprint planning | Game project management, workflow | | `game-sm` | Game Scrum Master | Game story creation, sprint planning | Game project management, workflow |
| `game-architect` | Game Architect | Unity system design, technical architecture | Complex Unity systems, performance planning | | `game-architect` | Game Architect | Unity system design, technical architecture | Complex Unity systems, performance planning |
**Note**: For QA and other roles, use the core BMad agents (e.g., `@qa` from bmad-core). **Note**: For QA and other roles, use the core BMad agents (e.g., `@qa` from .bmad-core).
### Game Agent Interaction Commands ### Game Agent Interaction Commands