ros/BMAD-METHOD
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix: standardize on file extension .yaml instead of a mix of yml and yaml

Browse Source
This commit is contained in:
Brian Madison
2025-07-02 19:59:49 -05:00
parent ffae072143
commit a4c0b1839d
73 changed files with 247 additions and 247 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
dist/agents/analyst.txt vendored
View File

@@ -665,7 +665,7 @@ Generate documents from templates by EXECUTING (not just reading) embedded instr
### 0. Check Workflow Plan (if configured)
[[LLM: Check if plan tracking is enabled in core-config.yml]]
[[LLM: Check if plan tracking is enabled in core-config.yaml]]
- If `workflow.trackProgress: true`, check for active plan using utils#plan-management
- If plan exists and this document creation is part of the plan:
@@ -2113,11 +2113,11 @@ npx bmad-method install
5. **MUST switch to Dev agent** for implementation
6. Keep planning and coding in separate chat sessions
## Core Configuration (core-config.yml)
## Core Configuration (core-config.yaml)
**New in V4**: The `bmad-core/core-config.yml` file is a critical innovation that enables BMAD to work seamlessly with any project structure, providing maximum flexibility and backwards compatibility.
**New in V4**: The `bmad-core/core-config.yaml` file is a critical innovation that enables BMAD to work seamlessly with any project structure, providing maximum flexibility and backwards compatibility.
### What is core-config.yml?
### What is core-config.yaml?
This configuration file acts as a map for BMAD agents, telling them exactly where to find your project documents and how they're structured. It enables:
@@ -2289,7 +2289,7 @@ The BMAD-Method is built around a modular architecture centered on the `bmad-cor
#### 2. Agent Teams (`bmad-core/agent-teams/`)
- **Purpose**: Define collections of agents bundled together for specific purposes
- **Examples**: `team-all.yml` (comprehensive bundle), `team-fullstack.yml` (full-stack development)
- **Examples**: `team-all.yaml` (comprehensive bundle), `team-fullstack.yaml` (full-stack development)
- **Usage**: Creates pre-packaged contexts for web UI environments
#### 3. Workflows (`bmad-core/workflows/`)

10
dist/agents/architect.txt vendored
View File

@@ -120,7 +120,7 @@ Generate documents from templates by EXECUTING (not just reading) embedded instr
### 0. Check Workflow Plan (if configured)
[[LLM: Check if plan tracking is enabled in core-config.yml]]
[[LLM: Check if plan tracking is enabled in core-config.yaml]]
- If `workflow.trackProgress: true`, check for active plan using utils#plan-management
- If plan exists and this document creation is part of the plan:
@@ -1315,7 +1315,7 @@ After presenting the structure, apply `tasks#advanced-elicitation` protocol to r
{{project-root}}/
├── .github/ # CI/CD workflows
│ └── workflows/
│ └── main.yml
│ └── main.yaml
├── .vscode/ # VSCode settings (optional)
│ └── settings.json
├── build/ # Compiled output (git-ignored)
@@ -2164,7 +2164,7 @@ Use appropriate format for the chosen API style. If no API (e.g., static site),
^^CONDITION: has_rest_api^^
```yml
```yaml
openapi: 3.0.0
info:
title:
@@ -2520,8 +2520,8 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
{{project-name}}/
├── .github/ # CI/CD workflows
│ └── workflows/
│ ├── ci.yml
│ └── deploy.yml
│ ├── ci.yaml
│ └── deploy.yaml
├── apps/ # Application packages
│ ├── web/ # Frontend application
│ │ ├── src/

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

@@ -1199,7 +1199,7 @@ Generate documents from templates by EXECUTING (not just reading) embedded instr
### 0. Check Workflow Plan (if configured)
[[LLM: Check if plan tracking is enabled in core-config.yml]]
[[LLM: Check if plan tracking is enabled in core-config.yaml]]
- If `workflow.trackProgress: true`, check for active plan using utils#plan-management
- If plan exists and this document creation is part of the plan:
@@ -1900,12 +1900,12 @@ To identify the next logical story based on project progress and epic definition
[[LLM: CRITICAL - This MUST be your first step]]
- Load `.bmad-core/core-config.yml` from the project root
- Load `.bmad-core/core-config.yaml` from the project root
- If the file does not exist:
- HALT and inform the user: "core-config.yml not found. This file is required for story creation. You can:
1. Copy it from GITHUB BMAD-METHOD/bmad-core/core-config.yml and configure it for your project
- HALT and inform the user: "core-config.yaml not found. This file is required for story creation. You can:
1. Copy it from GITHUB BMAD-METHOD/bmad-core/core-config.yaml and configure it for your project
2. Run the BMAD installer against your project to upgrade and add the file automatically
Please add and configure core-config.yml before proceeding."
Please add and configure core-config.yaml before proceeding."
- Extract the following key configurations:
- `devStoryLocation`: Where to save story files
- `prd.prdSharded`: Whether PRD is sharded or monolithic
@@ -2510,20 +2510,20 @@ Would you like to proceed with documentation indexing? Please provide the requir
## Primary Method: Automatic with markdown-tree
[[LLM: First, check if markdownExploder is set to true in bmad-core/core-config.yml. If it is, attempt to run the command: `md-tree explode {input file} {output path}`.
[[LLM: First, check if markdownExploder is set to true in bmad-core/core-config.yaml. If it is, attempt to run the command: `md-tree explode {input file} {output path}`.
If the command succeeds, inform the user that the document has been sharded successfully and STOP - do not proceed further.
If the command fails (especially with an error indicating the command is not found or not available), inform the user: "The markdownExploder setting is enabled but the md-tree command is not available. Please either:
1. Install @kayvan/markdown-tree-parser globally with: `npm install -g @kayvan/markdown-tree-parser`
2. Or set markdownExploder to false in bmad-core/core-config.yml
2. Or set markdownExploder to false in bmad-core/core-config.yaml
**IMPORTANT: STOP HERE - do not proceed with manual sharding until one of the above actions is taken.**"
If markdownExploder is set to false, inform the user: "The markdownExploder setting is currently false. For better performance and reliability, you should:
1. Set markdownExploder to true in bmad-core/core-config.yml
1. Set markdownExploder to true in bmad-core/core-config.yaml
2. Install @kayvan/markdown-tree-parser globally with: `npm install -g @kayvan/markdown-tree-parser`
I will now proceed with the manual sharding process."
@@ -2704,7 +2704,7 @@ Update the status of steps in an active workflow plan, mark completions, add not
### 0. Load Plan Configuration
[[LLM: First load core-config.yml to get plan settings]]
[[LLM: First load core-config.yaml to get plan settings]]
Check workflow configuration:
@@ -3343,7 +3343,7 @@ After presenting the structure, apply `tasks#advanced-elicitation` protocol to r
{{project-root}}/
├── .github/ # CI/CD workflows
│ └── workflows/
│ └── main.yml
│ └── main.yaml
├── .vscode/ # VSCode settings (optional)
│ └── settings.json
├── build/ # Compiled output (git-ignored)
@@ -5718,7 +5718,7 @@ Use appropriate format for the chosen API style. If no API (e.g., static site),
^^CONDITION: has_rest_api^^
```yml
```yaml
openapi: 3.0.0
info:
title:
@@ -6074,8 +6074,8 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
{{project-name}}/
├── .github/ # CI/CD workflows
│ └── workflows/
│ ├── ci.yml
│ └── deploy.yml
│ ├── ci.yaml
│ └── deploy.yaml
├── apps/ # Application packages
│ ├── web/ # Frontend application
│ │ ├── src/
@@ -9104,11 +9104,11 @@ npx bmad-method install
5. **MUST switch to Dev agent** for implementation
6. Keep planning and coding in separate chat sessions
## Core Configuration (core-config.yml)
## Core Configuration (core-config.yaml)
**New in V4**: The `bmad-core/core-config.yml` file is a critical innovation that enables BMAD to work seamlessly with any project structure, providing maximum flexibility and backwards compatibility.
**New in V4**: The `bmad-core/core-config.yaml` file is a critical innovation that enables BMAD to work seamlessly with any project structure, providing maximum flexibility and backwards compatibility.
### What is core-config.yml?
### What is core-config.yaml?
This configuration file acts as a map for BMAD agents, telling them exactly where to find your project documents and how they're structured. It enables:
@@ -9280,7 +9280,7 @@ The BMAD-Method is built around a modular architecture centered on the `bmad-cor
#### 2. Agent Teams (`bmad-core/agent-teams/`)
- **Purpose**: Define collections of agents bundled together for specific purposes
- **Examples**: `team-all.yml` (comprehensive bundle), `team-fullstack.yml` (full-stack development)
- **Examples**: `team-all.yaml` (comprehensive bundle), `team-fullstack.yaml` (full-stack development)
- **Usage**: Creates pre-packaged contexts for web UI environments
#### 3. Workflows (`bmad-core/workflows/`)
@@ -9714,7 +9714,7 @@ Provides utilities for agents and tasks to interact with workflow plans, check p
```
Check for workflow plan:
1. Look for docs/workflow-plan.md (default location)
2. Check core-config.yml for custom plan location
2. Check core-config.yaml for custom plan location
3. Return plan status (exists/not exists)
```

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

@@ -290,7 +290,7 @@ Generate documents from templates by EXECUTING (not just reading) embedded instr
### 0. Check Workflow Plan (if configured)
[[LLM: Check if plan tracking is enabled in core-config.yml]]
[[LLM: Check if plan tracking is enabled in core-config.yaml]]
- If `workflow.trackProgress: true`, check for active plan using utils#plan-management
- If plan exists and this document creation is part of the plan:
@@ -742,7 +742,7 @@ Update the status of steps in an active workflow plan, mark completions, add not
### 0. Load Plan Configuration
[[LLM: First load core-config.yml to get plan settings]]
[[LLM: First load core-config.yaml to get plan settings]]
Check workflow configuration:
@@ -1146,11 +1146,11 @@ npx bmad-method install
5. **MUST switch to Dev agent** for implementation
6. Keep planning and coding in separate chat sessions
## Core Configuration (core-config.yml)
## Core Configuration (core-config.yaml)
**New in V4**: The `bmad-core/core-config.yml` file is a critical innovation that enables BMAD to work seamlessly with any project structure, providing maximum flexibility and backwards compatibility.
**New in V4**: The `bmad-core/core-config.yaml` file is a critical innovation that enables BMAD to work seamlessly with any project structure, providing maximum flexibility and backwards compatibility.
### What is core-config.yml?
### What is core-config.yaml?
This configuration file acts as a map for BMAD agents, telling them exactly where to find your project documents and how they're structured. It enables:
@@ -1322,7 +1322,7 @@ The BMAD-Method is built around a modular architecture centered on the `bmad-cor
#### 2. Agent Teams (`bmad-core/agent-teams/`)
- **Purpose**: Define collections of agents bundled together for specific purposes
- **Examples**: `team-all.yml` (comprehensive bundle), `team-fullstack.yml` (full-stack development)
- **Examples**: `team-all.yaml` (comprehensive bundle), `team-fullstack.yaml` (full-stack development)
- **Usage**: Creates pre-packaged contexts for web UI environments
#### 3. Workflows (`bmad-core/workflows/`)
@@ -1750,7 +1750,7 @@ Provides utilities for agents and tasks to interact with workflow plans, check p
```
Check for workflow plan:
1. Look for docs/workflow-plan.md (default location)
2. Check core-config.yml for custom plan location
2. Check core-config.yaml for custom plan location
3. Return plan status (exists/not exists)
```

2
dist/agents/dev.txt vendored
View File

@@ -53,7 +53,7 @@ agent:
customization: null
startup:
- Announce: Greet the user with your name and role, and inform of the *help command.
- CRITICAL: Load .bmad-core/core-config.yml and read devLoadAlwaysFiles list and devDebugLog values
- CRITICAL: Load .bmad-core/core-config.yaml and read devLoadAlwaysFiles list and devDebugLog values
- CRITICAL: Load ONLY files specified in devLoadAlwaysFiles. If any missing, inform user but continue
- CRITICAL: Do NOT load any story files during startup unless user requested you do
- CRITICAL: Do NOT begin development until told to proceed

8
dist/agents/pm.txt vendored
View File

@@ -117,7 +117,7 @@ Generate documents from templates by EXECUTING (not just reading) embedded instr
### 0. Check Workflow Plan (if configured)
[[LLM: Check if plan tracking is enabled in core-config.yml]]
[[LLM: Check if plan tracking is enabled in core-config.yaml]]
- If `workflow.trackProgress: true`, check for active plan using utils#plan-management
- If plan exists and this document creation is part of the plan:
@@ -993,20 +993,20 @@ The LLM will:
## Primary Method: Automatic with markdown-tree
[[LLM: First, check if markdownExploder is set to true in bmad-core/core-config.yml. If it is, attempt to run the command: `md-tree explode {input file} {output path}`.
[[LLM: First, check if markdownExploder is set to true in bmad-core/core-config.yaml. If it is, attempt to run the command: `md-tree explode {input file} {output path}`.
If the command succeeds, inform the user that the document has been sharded successfully and STOP - do not proceed further.
If the command fails (especially with an error indicating the command is not found or not available), inform the user: "The markdownExploder setting is enabled but the md-tree command is not available. Please either:
1. Install @kayvan/markdown-tree-parser globally with: `npm install -g @kayvan/markdown-tree-parser`
2. Or set markdownExploder to false in bmad-core/core-config.yml
2. Or set markdownExploder to false in bmad-core/core-config.yaml
**IMPORTANT: STOP HERE - do not proceed with manual sharding until one of the above actions is taken.**"
If markdownExploder is set to false, inform the user: "The markdownExploder setting is currently false. For better performance and reliability, you should:
1. Set markdownExploder to true in bmad-core/core-config.yml
1. Set markdownExploder to true in bmad-core/core-config.yaml
2. Install @kayvan/markdown-tree-parser globally with: `npm install -g @kayvan/markdown-tree-parser`
I will now proceed with the manual sharding process."

6
dist/agents/po.txt vendored
View File

@@ -208,20 +208,20 @@ The LLM will:
## Primary Method: Automatic with markdown-tree
[[LLM: First, check if markdownExploder is set to true in bmad-core/core-config.yml. If it is, attempt to run the command: `md-tree explode {input file} {output path}`.
[[LLM: First, check if markdownExploder is set to true in bmad-core/core-config.yaml. If it is, attempt to run the command: `md-tree explode {input file} {output path}`.
If the command succeeds, inform the user that the document has been sharded successfully and STOP - do not proceed further.
If the command fails (especially with an error indicating the command is not found or not available), inform the user: "The markdownExploder setting is enabled but the md-tree command is not available. Please either:
1. Install @kayvan/markdown-tree-parser globally with: `npm install -g @kayvan/markdown-tree-parser`
2. Or set markdownExploder to false in bmad-core/core-config.yml
2. Or set markdownExploder to false in bmad-core/core-config.yaml
**IMPORTANT: STOP HERE - do not proceed with manual sharding until one of the above actions is taken.**"
If markdownExploder is set to false, inform the user: "The markdownExploder setting is currently false. For better performance and reliability, you should:
1. Set markdownExploder to true in bmad-core/core-config.yml
1. Set markdownExploder to true in bmad-core/core-config.yaml
2. Install @kayvan/markdown-tree-parser globally with: `npm install -g @kayvan/markdown-tree-parser`
I will now proceed with the manual sharding process."

8
dist/agents/sm.txt vendored
View File

@@ -102,12 +102,12 @@ To identify the next logical story based on project progress and epic definition
[[LLM: CRITICAL - This MUST be your first step]]
- Load `.bmad-core/core-config.yml` from the project root
- Load `.bmad-core/core-config.yaml` from the project root
- If the file does not exist:
- HALT and inform the user: "core-config.yml not found. This file is required for story creation. You can:
1. Copy it from GITHUB BMAD-METHOD/bmad-core/core-config.yml and configure it for your project
- HALT and inform the user: "core-config.yaml not found. This file is required for story creation. You can:
1. Copy it from GITHUB BMAD-METHOD/bmad-core/core-config.yaml and configure it for your project
2. Run the BMAD installer against your project to upgrade and add the file automatically
Please add and configure core-config.yml before proceeding."
Please add and configure core-config.yaml before proceeding."
- Extract the following key configurations:
- `devStoryLocation`: Where to save story files
- `prd.prdSharded`: Whether PRD is sharded or monolithic

2
dist/agents/ux-expert.txt vendored
View File

@@ -477,7 +477,7 @@ Generate documents from templates by EXECUTING (not just reading) embedded instr
### 0. Check Workflow Plan (if configured)
[[LLM: Check if plan tracking is enabled in core-config.yml]]
[[LLM: Check if plan tracking is enabled in core-config.yaml]]
- If `workflow.trackProgress: true`, check for active plan using utils#plan-management
- If plan exists and this document creation is part of the plan:

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

@@ -117,7 +117,7 @@ Generate documents from templates by EXECUTING (not just reading) embedded instr
### 0. Check Workflow Plan (if configured)
[[LLM: Check if plan tracking is enabled in core-config.yml]]
[[LLM: Check if plan tracking is enabled in core-config.yaml]]
- If `workflow.trackProgress: true`, check for active plan using utils#plan-management
- If plan exists and this document creation is part of the plan:

14
dist/expansion-packs/bmad-2d-phaser-game-dev/teams/phaser-2d-nodejs-game-team.txt vendored
View File

@@ -1004,7 +1004,7 @@ Generate documents from templates by EXECUTING (not just reading) embedded instr
### 0. Check Workflow Plan (if configured)
[[LLM: Check if plan tracking is enabled in core-config.yml]]
[[LLM: Check if plan tracking is enabled in core-config.yaml]]
- If `workflow.trackProgress: true`, check for active plan using utils#plan-management
- If plan exists and this document creation is part of the plan:
@@ -2969,7 +2969,7 @@ Update the status of steps in an active workflow plan, mark completions, add not
### 0. Load Plan Configuration
[[LLM: First load core-config.yml to get plan settings]]
[[LLM: First load core-config.yaml to get plan settings]]
Check workflow configuration:
@@ -3225,7 +3225,7 @@ Provides utilities for agents and tasks to interact with workflow plans, check p
```
Check for workflow plan:
1. Look for docs/workflow-plan.md (default location)
2. Check core-config.yml for custom plan location
2. Check core-config.yaml for custom plan location
3. Return plan status (exists/not exists)
```
@@ -7110,7 +7110,7 @@ class {{ClassName}} extends {{PhaseClass}} {
- {{future_optimization_1}}
==================== END: templates#game-story-tmpl ====================
==================== START: workflows#game-dev-greenfield ====================
==================== START: workflows#game-dev-greenfield.yaml ====================
workflow:
id: game-dev-greenfield
name: Game Development - Greenfield Project
@@ -7294,9 +7294,9 @@ workflow:
- Testing framework in place
- Team roles and responsibilities defined
- First implementation stories created and ready
==================== END: workflows#game-dev-greenfield ====================
==================== END: workflows#game-dev-greenfield.yaml ====================
==================== START: workflows#game-prototype ====================
==================== START: workflows#game-prototype.yaml ====================
workflow:
id: game-prototype
name: Game Prototype Development
@@ -7472,4 +7472,4 @@ workflow:
technical_to_stories: Technical plan complete. Create focused implementation stories for prototype development.
stories_to_implementation: Stories ready. Begin iterative implementation with frequent playtesting and design validation.
prototype_to_evaluation: Prototype playable. Evaluate core mechanics, gather feedback, and determine next development steps.
==================== END: workflows#game-prototype ====================
==================== END: workflows#game-prototype.yaml ====================

20
dist/expansion-packs/bmad-creator-tools/agents/bmad-the-creator.txt vendored
View File

@@ -586,7 +586,7 @@ IMPORTANT: Only proceed after plan.md is approved
expansion-packs/
└── {pack-name}/
├── plan.md (ALREADY CREATED)
├── manifest.yml
├── manifest.yaml
├── README.md
├── agents/
│ ├── {pack-name}-orchestrator.md (REQUIRED - Custom themed orchestrator)
@@ -609,13 +609,13 @@ expansion-packs/
├── workflows/
│ └── {domain}-workflow.md (REQUIRED if multiple agents)
└── agent-teams/
└── {domain}-team.yml (REQUIRED if multiple agents)
└── {domain}-team.yaml (REQUIRED if multiple agents)
```
#### 3.2 Create Manifest
Create `manifest.yml`:
Create `manifest.yaml`:
```yaml
name: {pack-name}
@@ -658,7 +658,7 @@ files:
- {domain}-workflow.md # REQUIRED if multiple agents - decision trees
agent-teams:
- {domain}-team.yml # REQUIRED if multiple agents - team config
- {domain}-team.yaml # REQUIRED if multiple agents - team config
# Data files users must provide (in their bmad-core/data/ directory)
required_user_data:
@@ -794,7 +794,7 @@ cp common/utils/workflow-management.md expansion-packs/{pack-name}/utils/
1. Design decision trees for workflow branching
2. Create handoff protocols to specialist agents
3. Implement validation loops and quality checkpoints
4. **If multiple agents**: Create team configuration in `agent-teams/{domain}-team.yml`
4. **If multiple agents**: Create team configuration in `agent-teams/{domain}-team.yaml`
5. **If multiple agents**: Create workflow in `workflows/{domain}-workflow.md`
6. Ensure orchestrator references workflow-management utility
7. Verify ALL referenced tasks exist (including core utilities)
@@ -965,7 +965,7 @@ Before declaring complete:
1. [ ] Decision trees and workflow orchestration complete
2. [ ] Knowledge base files embedded (best practices, terminology, standards)
3. [ ] Manifest.yml reflects all components and dependencies
3. [ ] Manifest.yaml reflects all components and dependencies
4. [ ] All items in plan.md marked complete
5. [ ] No orphaned tasks or templates
@@ -1072,7 +1072,7 @@ These files are automatically available to all agents and don't require user set
```text
healthcare/
├── plan.md (Created first for approval)
├── manifest.yml (with dependency mapping and character descriptions)
├── manifest.yaml (with dependency mapping and character descriptions)
├── README.md (featuring character introductions and numbered options)
├── agents/
│ ├── healthcare-orchestrator.md (Dr. Sarah Chen - YAML-in-Markdown)
@@ -1098,7 +1098,7 @@ healthcare/
│ ├── clinical-trial-workflow.md (decision trees with Mermaid diagrams)
│ └── compliance-audit-workflow.md (handoff protocols and quality gates)
└── agent-teams/
└── healthcare-team.yml (coordinated team configurations)
└── healthcare-team.yaml (coordinated team configurations)
Required user data files (bmad-core/data/):
- medical-terminology.md (institution-specific terms and abbreviations)
@@ -1309,7 +1309,7 @@ Embedded knowledge (automatic):
- [ ] All agent references verified (tasks, templates, data, checklists)
- [ ] Data requirements documented with validation criteria and examples
- [ ] README includes character introductions and numbered options explanation
- [ ] manifest.yml reflects actual files with dependency mapping and character descriptions
- [ ] manifest.yaml reflects actual files with dependency mapping and character descriptions
**Advanced Quality Gates:**
@@ -1732,7 +1732,7 @@ Present these numbered options to the user:
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
```yaml
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

4
dist/expansion-packs/bmad-infrastructure-devops/agents/infra-devops-platform.txt vendored
View File

@@ -118,7 +118,7 @@ Generate documents from templates by EXECUTING (not just reading) embedded instr
### 0. Check Workflow Plan (if configured)
[[LLM: Check if plan tracking is enabled in core-config.yml]]
[[LLM: Check if plan tracking is enabled in core-config.yaml]]
- If `workflow.trackProgress: true`, check for active plan using utils#plan-management
- If plan exists and this document creation is part of the plan:
@@ -1300,7 +1300,7 @@ kind: ConfigMap
metadata:
name: prometheus-config
data:
prometheus.yml: |
prometheus.yaml: |
global:
scrape_interval: {{scrape_interval}}
scrape_configs:

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

@@ -337,7 +337,7 @@ agent:
customization: null
startup:
- Announce: Greet the user with your name and role, and inform of the *help command.
- CRITICAL: Load .bmad-core/core-config.yml and read devLoadAlwaysFiles list and devDebugLog values
- CRITICAL: Load .bmad-core/core-config.yaml and read devLoadAlwaysFiles list and devDebugLog values
- CRITICAL: Load ONLY files specified in devLoadAlwaysFiles. If any missing, inform user but continue
- CRITICAL: Do NOT load any story files during startup unless user requested you do
- CRITICAL: Do NOT begin development until told to proceed
@@ -782,7 +782,7 @@ Generate documents from templates by EXECUTING (not just reading) embedded instr
### 0. Check Workflow Plan (if configured)
[[LLM: Check if plan tracking is enabled in core-config.yml]]
[[LLM: Check if plan tracking is enabled in core-config.yaml]]
- If `workflow.trackProgress: true`, check for active plan using utils#plan-management
- If plan exists and this document creation is part of the plan:
@@ -1234,7 +1234,7 @@ Update the status of steps in an active workflow plan, mark completions, add not
### 0. Load Plan Configuration
[[LLM: First load core-config.yml to get plan settings]]
[[LLM: First load core-config.yaml to get plan settings]]
Check workflow configuration:
@@ -1638,11 +1638,11 @@ npx bmad-method install
5. **MUST switch to Dev agent** for implementation
6. Keep planning and coding in separate chat sessions
## Core Configuration (core-config.yml)
## Core Configuration (core-config.yaml)
**New in V4**: The `bmad-core/core-config.yml` file is a critical innovation that enables BMAD to work seamlessly with any project structure, providing maximum flexibility and backwards compatibility.
**New in V4**: The `bmad-core/core-config.yaml` file is a critical innovation that enables BMAD to work seamlessly with any project structure, providing maximum flexibility and backwards compatibility.
### What is core-config.yml?
### What is core-config.yaml?
This configuration file acts as a map for BMAD agents, telling them exactly where to find your project documents and how they're structured. It enables:
@@ -1814,7 +1814,7 @@ The BMAD-Method is built around a modular architecture centered on the `bmad-cor
#### 2. Agent Teams (`bmad-core/agent-teams/`)
- **Purpose**: Define collections of agents bundled together for specific purposes
- **Examples**: `team-all.yml` (comprehensive bundle), `team-fullstack.yml` (full-stack development)
- **Examples**: `team-all.yaml` (comprehensive bundle), `team-fullstack.yaml` (full-stack development)
- **Usage**: Creates pre-packaged contexts for web UI environments
#### 3. Workflows (`bmad-core/workflows/`)
@@ -2242,7 +2242,7 @@ Provides utilities for agents and tasks to interact with workflow plans, check p
```
Check for workflow plan:
1. Look for docs/workflow-plan.md (default location)
2. Check core-config.yml for custom plan location
2. Check core-config.yaml for custom plan location
3. Return plan status (exists/not exists)
```
@@ -4706,7 +4706,7 @@ After presenting the structure, apply `tasks#advanced-elicitation` protocol to r
{{project-root}}/
├── .github/ # CI/CD workflows
│ └── workflows/
│ └── main.yml
│ └── main.yaml
├── .vscode/ # VSCode settings (optional)
│ └── settings.json
├── build/ # Compiled output (git-ignored)
@@ -5555,7 +5555,7 @@ Use appropriate format for the chosen API style. If no API (e.g., static site),
^^CONDITION: has_rest_api^^
```yml
```yaml
openapi: 3.0.0
info:
title:
@@ -5911,8 +5911,8 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
{{project-name}}/
├── .github/ # CI/CD workflows
│ └── workflows/
│ ├── ci.yml
│ └── deploy.yml
│ ├── ci.yaml
│ └── deploy.yaml
├── apps/ # Application packages
│ ├── web/ # Frontend application
│ │ ├── src/
@@ -7788,20 +7788,20 @@ The story creation is successful when:
## Primary Method: Automatic with markdown-tree
[[LLM: First, check if markdownExploder is set to true in bmad-core/core-config.yml. If it is, attempt to run the command: `md-tree explode {input file} {output path}`.
[[LLM: First, check if markdownExploder is set to true in bmad-core/core-config.yaml. If it is, attempt to run the command: `md-tree explode {input file} {output path}`.
If the command succeeds, inform the user that the document has been sharded successfully and STOP - do not proceed further.
If the command fails (especially with an error indicating the command is not found or not available), inform the user: "The markdownExploder setting is enabled but the md-tree command is not available. Please either:
1. Install @kayvan/markdown-tree-parser globally with: `npm install -g @kayvan/markdown-tree-parser`
2. Or set markdownExploder to false in bmad-core/core-config.yml
2. Or set markdownExploder to false in bmad-core/core-config.yaml
**IMPORTANT: STOP HERE - do not proceed with manual sharding until one of the above actions is taken.**"
If markdownExploder is set to false, inform the user: "The markdownExploder setting is currently false. For better performance and reliability, you should:
1. Set markdownExploder to true in bmad-core/core-config.yml
1. Set markdownExploder to true in bmad-core/core-config.yaml
2. Install @kayvan/markdown-tree-parser globally with: `npm install -g @kayvan/markdown-tree-parser`
I will now proceed with the manual sharding process."
@@ -9675,12 +9675,12 @@ To identify the next logical story based on project progress and epic definition
[[LLM: CRITICAL - This MUST be your first step]]
- Load `.bmad-core/core-config.yml` from the project root
- Load `.bmad-core/core-config.yaml` from the project root
- If the file does not exist:
- HALT and inform the user: "core-config.yml not found. This file is required for story creation. You can:
1. Copy it from GITHUB BMAD-METHOD/bmad-core/core-config.yml and configure it for your project
- HALT and inform the user: "core-config.yaml not found. This file is required for story creation. You can:
1. Copy it from GITHUB BMAD-METHOD/bmad-core/core-config.yaml and configure it for your project
2. Run the BMAD installer against your project to upgrade and add the file automatically
Please add and configure core-config.yml before proceeding."
Please add and configure core-config.yaml before proceeding."
- Extract the following key configurations:
- `devStoryLocation`: Where to save story files
- `prd.prdSharded`: Whether PRD is sharded or monolithic

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

@@ -626,7 +626,7 @@ Generate documents from templates by EXECUTING (not just reading) embedded instr
### 0. Check Workflow Plan (if configured)
[[LLM: Check if plan tracking is enabled in core-config.yml]]
[[LLM: Check if plan tracking is enabled in core-config.yaml]]
- If `workflow.trackProgress: true`, check for active plan using utils#plan-management
- If plan exists and this document creation is part of the plan:
@@ -1078,7 +1078,7 @@ Update the status of steps in an active workflow plan, mark completions, add not
### 0. Load Plan Configuration
[[LLM: First load core-config.yml to get plan settings]]
[[LLM: First load core-config.yaml to get plan settings]]
Check workflow configuration:
@@ -1482,11 +1482,11 @@ npx bmad-method install
5. **MUST switch to Dev agent** for implementation
6. Keep planning and coding in separate chat sessions
## Core Configuration (core-config.yml)
## Core Configuration (core-config.yaml)
**New in V4**: The `bmad-core/core-config.yml` file is a critical innovation that enables BMAD to work seamlessly with any project structure, providing maximum flexibility and backwards compatibility.
**New in V4**: The `bmad-core/core-config.yaml` file is a critical innovation that enables BMAD to work seamlessly with any project structure, providing maximum flexibility and backwards compatibility.
### What is core-config.yml?
### What is core-config.yaml?
This configuration file acts as a map for BMAD agents, telling them exactly where to find your project documents and how they're structured. It enables:
@@ -1658,7 +1658,7 @@ The BMAD-Method is built around a modular architecture centered on the `bmad-cor
#### 2. Agent Teams (`bmad-core/agent-teams/`)
- **Purpose**: Define collections of agents bundled together for specific purposes
- **Examples**: `team-all.yml` (comprehensive bundle), `team-fullstack.yml` (full-stack development)
- **Examples**: `team-all.yaml` (comprehensive bundle), `team-fullstack.yaml` (full-stack development)
- **Usage**: Creates pre-packaged contexts for web UI environments
#### 3. Workflows (`bmad-core/workflows/`)
@@ -2086,7 +2086,7 @@ Provides utilities for agents and tasks to interact with workflow plans, check p
```
Check for workflow plan:
1. Look for docs/workflow-plan.md (default location)
2. Check core-config.yml for custom plan location
2. Check core-config.yaml for custom plan location
3. Return plan status (exists/not exists)
```
@@ -4551,20 +4551,20 @@ The LLM will:
## Primary Method: Automatic with markdown-tree
[[LLM: First, check if markdownExploder is set to true in bmad-core/core-config.yml. If it is, attempt to run the command: `md-tree explode {input file} {output path}`.
[[LLM: First, check if markdownExploder is set to true in bmad-core/core-config.yaml. If it is, attempt to run the command: `md-tree explode {input file} {output path}`.
If the command succeeds, inform the user that the document has been sharded successfully and STOP - do not proceed further.
If the command fails (especially with an error indicating the command is not found or not available), inform the user: "The markdownExploder setting is enabled but the md-tree command is not available. Please either:
1. Install @kayvan/markdown-tree-parser globally with: `npm install -g @kayvan/markdown-tree-parser`
2. Or set markdownExploder to false in bmad-core/core-config.yml
2. Or set markdownExploder to false in bmad-core/core-config.yaml
**IMPORTANT: STOP HERE - do not proceed with manual sharding until one of the above actions is taken.**"
If markdownExploder is set to false, inform the user: "The markdownExploder setting is currently false. For better performance and reliability, you should:
1. Set markdownExploder to true in bmad-core/core-config.yml
1. Set markdownExploder to true in bmad-core/core-config.yaml
2. Install @kayvan/markdown-tree-parser globally with: `npm install -g @kayvan/markdown-tree-parser`
I will now proceed with the manual sharding process."
@@ -6646,7 +6646,7 @@ After presenting the structure, apply `tasks#advanced-elicitation` protocol to r
{{project-root}}/
├── .github/ # CI/CD workflows
│ └── workflows/
│ └── main.yml
│ └── main.yaml
├── .vscode/ # VSCode settings (optional)
│ └── settings.json
├── build/ # Compiled output (git-ignored)
@@ -7495,7 +7495,7 @@ Use appropriate format for the chosen API style. If no API (e.g., static site),
^^CONDITION: has_rest_api^^
```yml
```yaml
openapi: 3.0.0
info:
title:
@@ -7851,8 +7851,8 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
{{project-name}}/
├── .github/ # CI/CD workflows
│ └── workflows/
│ ├── ci.yml
│ └── deploy.yml
│ ├── ci.yaml
│ └── deploy.yaml
├── apps/ # Application packages
│ ├── web/ # Frontend application
│ │ ├── src/

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

@@ -319,7 +319,7 @@ agent:
customization: null
startup:
- Announce: Greet the user with your name and role, and inform of the *help command.
- CRITICAL: Load .bmad-core/core-config.yml and read devLoadAlwaysFiles list and devDebugLog values
- CRITICAL: Load .bmad-core/core-config.yaml and read devLoadAlwaysFiles list and devDebugLog values
- CRITICAL: Load ONLY files specified in devLoadAlwaysFiles. If any missing, inform user but continue
- CRITICAL: Do NOT load any story files during startup unless user requested you do
- CRITICAL: Do NOT begin development until told to proceed
@@ -526,7 +526,7 @@ Generate documents from templates by EXECUTING (not just reading) embedded instr
### 0. Check Workflow Plan (if configured)
[[LLM: Check if plan tracking is enabled in core-config.yml]]
[[LLM: Check if plan tracking is enabled in core-config.yaml]]
- If `workflow.trackProgress: true`, check for active plan using utils#plan-management
- If plan exists and this document creation is part of the plan:
@@ -978,7 +978,7 @@ Update the status of steps in an active workflow plan, mark completions, add not
### 0. Load Plan Configuration
[[LLM: First load core-config.yml to get plan settings]]
[[LLM: First load core-config.yaml to get plan settings]]
Check workflow configuration:
@@ -1382,11 +1382,11 @@ npx bmad-method install
5. **MUST switch to Dev agent** for implementation
6. Keep planning and coding in separate chat sessions
## Core Configuration (core-config.yml)
## Core Configuration (core-config.yaml)
**New in V4**: The `bmad-core/core-config.yml` file is a critical innovation that enables BMAD to work seamlessly with any project structure, providing maximum flexibility and backwards compatibility.
**New in V4**: The `bmad-core/core-config.yaml` file is a critical innovation that enables BMAD to work seamlessly with any project structure, providing maximum flexibility and backwards compatibility.
### What is core-config.yml?
### What is core-config.yaml?
This configuration file acts as a map for BMAD agents, telling them exactly where to find your project documents and how they're structured. It enables:
@@ -1558,7 +1558,7 @@ The BMAD-Method is built around a modular architecture centered on the `bmad-cor
#### 2. Agent Teams (`bmad-core/agent-teams/`)
- **Purpose**: Define collections of agents bundled together for specific purposes
- **Examples**: `team-all.yml` (comprehensive bundle), `team-fullstack.yml` (full-stack development)
- **Examples**: `team-all.yaml` (comprehensive bundle), `team-fullstack.yaml` (full-stack development)
- **Usage**: Creates pre-packaged contexts for web UI environments
#### 3. Workflows (`bmad-core/workflows/`)
@@ -1986,7 +1986,7 @@ Provides utilities for agents and tasks to interact with workflow plans, check p
```
Check for workflow plan:
1. Look for docs/workflow-plan.md (default location)
2. Check core-config.yml for custom plan location
2. Check core-config.yaml for custom plan location
3. Return plan status (exists/not exists)
```
@@ -2404,20 +2404,20 @@ The LLM will:
## Primary Method: Automatic with markdown-tree
[[LLM: First, check if markdownExploder is set to true in bmad-core/core-config.yml. If it is, attempt to run the command: `md-tree explode {input file} {output path}`.
[[LLM: First, check if markdownExploder is set to true in bmad-core/core-config.yaml. If it is, attempt to run the command: `md-tree explode {input file} {output path}`.
If the command succeeds, inform the user that the document has been sharded successfully and STOP - do not proceed further.
If the command fails (especially with an error indicating the command is not found or not available), inform the user: "The markdownExploder setting is enabled but the md-tree command is not available. Please either:
1. Install @kayvan/markdown-tree-parser globally with: `npm install -g @kayvan/markdown-tree-parser`
2. Or set markdownExploder to false in bmad-core/core-config.yml
2. Or set markdownExploder to false in bmad-core/core-config.yaml
**IMPORTANT: STOP HERE - do not proceed with manual sharding until one of the above actions is taken.**"
If markdownExploder is set to false, inform the user: "The markdownExploder setting is currently false. For better performance and reliability, you should:
1. Set markdownExploder to true in bmad-core/core-config.yml
1. Set markdownExploder to true in bmad-core/core-config.yaml
2. Install @kayvan/markdown-tree-parser globally with: `npm install -g @kayvan/markdown-tree-parser`
I will now proceed with the manual sharding process."
@@ -3690,12 +3690,12 @@ To identify the next logical story based on project progress and epic definition
[[LLM: CRITICAL - This MUST be your first step]]
- Load `.bmad-core/core-config.yml` from the project root
- Load `.bmad-core/core-config.yaml` from the project root
- If the file does not exist:
- HALT and inform the user: "core-config.yml not found. This file is required for story creation. You can:
1. Copy it from GITHUB BMAD-METHOD/bmad-core/core-config.yml and configure it for your project
- HALT and inform the user: "core-config.yaml not found. This file is required for story creation. You can:
1. Copy it from GITHUB BMAD-METHOD/bmad-core/core-config.yaml and configure it for your project
2. Run the BMAD installer against your project to upgrade and add the file automatically
Please add and configure core-config.yml before proceeding."
Please add and configure core-config.yaml before proceeding."
- Extract the following key configurations:
- `devStoryLocation`: Where to save story files
- `prd.prdSharded`: Whether PRD is sharded or monolithic

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

@@ -558,7 +558,7 @@ Generate documents from templates by EXECUTING (not just reading) embedded instr
### 0. Check Workflow Plan (if configured)
[[LLM: Check if plan tracking is enabled in core-config.yml]]
[[LLM: Check if plan tracking is enabled in core-config.yaml]]
- If `workflow.trackProgress: true`, check for active plan using utils#plan-management
- If plan exists and this document creation is part of the plan:
@@ -1010,7 +1010,7 @@ Update the status of steps in an active workflow plan, mark completions, add not
### 0. Load Plan Configuration
[[LLM: First load core-config.yml to get plan settings]]
[[LLM: First load core-config.yaml to get plan settings]]
Check workflow configuration:
@@ -1414,11 +1414,11 @@ npx bmad-method install
5. **MUST switch to Dev agent** for implementation
6. Keep planning and coding in separate chat sessions
## Core Configuration (core-config.yml)
## Core Configuration (core-config.yaml)
**New in V4**: The `bmad-core/core-config.yml` file is a critical innovation that enables BMAD to work seamlessly with any project structure, providing maximum flexibility and backwards compatibility.
**New in V4**: The `bmad-core/core-config.yaml` file is a critical innovation that enables BMAD to work seamlessly with any project structure, providing maximum flexibility and backwards compatibility.
### What is core-config.yml?
### What is core-config.yaml?
This configuration file acts as a map for BMAD agents, telling them exactly where to find your project documents and how they're structured. It enables:
@@ -1590,7 +1590,7 @@ The BMAD-Method is built around a modular architecture centered on the `bmad-cor
#### 2. Agent Teams (`bmad-core/agent-teams/`)
- **Purpose**: Define collections of agents bundled together for specific purposes
- **Examples**: `team-all.yml` (comprehensive bundle), `team-fullstack.yml` (full-stack development)
- **Examples**: `team-all.yaml` (comprehensive bundle), `team-fullstack.yaml` (full-stack development)
- **Usage**: Creates pre-packaged contexts for web UI environments
#### 3. Workflows (`bmad-core/workflows/`)
@@ -2018,7 +2018,7 @@ Provides utilities for agents and tasks to interact with workflow plans, check p
```
Check for workflow plan:
1. Look for docs/workflow-plan.md (default location)
2. Check core-config.yml for custom plan location
2. Check core-config.yaml for custom plan location
3. Return plan status (exists/not exists)
```
@@ -4483,20 +4483,20 @@ The LLM will:
## Primary Method: Automatic with markdown-tree
[[LLM: First, check if markdownExploder is set to true in bmad-core/core-config.yml. If it is, attempt to run the command: `md-tree explode {input file} {output path}`.
[[LLM: First, check if markdownExploder is set to true in bmad-core/core-config.yaml. If it is, attempt to run the command: `md-tree explode {input file} {output path}`.
If the command succeeds, inform the user that the document has been sharded successfully and STOP - do not proceed further.
If the command fails (especially with an error indicating the command is not found or not available), inform the user: "The markdownExploder setting is enabled but the md-tree command is not available. Please either:
1. Install @kayvan/markdown-tree-parser globally with: `npm install -g @kayvan/markdown-tree-parser`
2. Or set markdownExploder to false in bmad-core/core-config.yml
2. Or set markdownExploder to false in bmad-core/core-config.yaml
**IMPORTANT: STOP HERE - do not proceed with manual sharding until one of the above actions is taken.**"
If markdownExploder is set to false, inform the user: "The markdownExploder setting is currently false. For better performance and reliability, you should:
1. Set markdownExploder to true in bmad-core/core-config.yml
1. Set markdownExploder to true in bmad-core/core-config.yaml
2. Install @kayvan/markdown-tree-parser globally with: `npm install -g @kayvan/markdown-tree-parser`
I will now proceed with the manual sharding process."
@@ -6108,7 +6108,7 @@ After presenting the structure, apply `tasks#advanced-elicitation` protocol to r
{{project-root}}/
├── .github/ # CI/CD workflows
│ └── workflows/
│ └── main.yml
│ └── main.yaml
├── .vscode/ # VSCode settings (optional)
│ └── settings.json
├── build/ # Compiled output (git-ignored)
@@ -6957,7 +6957,7 @@ Use appropriate format for the chosen API style. If no API (e.g., static site),
^^CONDITION: has_rest_api^^
```yml
```yaml
openapi: 3.0.0
info:
title:
@@ -7313,8 +7313,8 @@ After presenting this section, apply `tasks#advanced-elicitation` protocol]]
{{project-name}}/
├── .github/ # CI/CD workflows
│ └── workflows/
│ ├── ci.yml
│ └── deploy.yml
│ ├── ci.yaml
│ └── deploy.yaml
├── apps/ # Application packages
│ ├── web/ # Frontend application
│ │ ├── src/