bmad-method 4.24.0 → 4.24.1

package/.vscode/settings.json

@@ -1,7 +1,13 @@
 {
-    "cSpell.words": [
-        "Agentic",
-        "elicitations",
-        "Shardable"
-    ]
+  "chat.agent.enabled": true,
+  "chat.agent.maxRequests": 15,
+  "github.copilot.chat.agent.runTasks": true,
+  "chat.mcp.discovery.enabled": true,
+  "github.copilot.chat.agent.autoFix": true,
+  "chat.tools.autoApprove": false,
+  "cSpell.words": [
+    "Agentic",
+    "elicitations",
+    "Shardable"
+  ]
 }

package/CHANGELOG.md

@@ -1,3 +1,12 @@
+## [4.24.1](https://github.com/bmadcode/BMAD-METHOD/compare/v4.24.0...v4.24.1) (2025-07-03)
+
+
+### Bug Fixes
+
+* centralized yamlExtraction function and all now fix character issues for windows ([e2985d6](https://github.com/bmadcode/BMAD-METHOD/commit/e2985d6093136575e8d8c91ce53c82abc4097de6))
+* filtering extension stripping logic update ([405954a](https://github.com/bmadcode/BMAD-METHOD/commit/405954ad924d8bd66f94c918643f6e9c091d4d09))
+* standardize on file extension .yaml instead of a mix of yml and yaml ([a4c0b18](https://github.com/bmadcode/BMAD-METHOD/commit/a4c0b1839d12d2ad21b7949aa30f4f7d82ec6c9c))
+
 # [4.24.0](https://github.com/bmadcode/BMAD-METHOD/compare/v4.23.0...v4.24.0) (2025-07-02)
 
 
@@ -213,7 +222,7 @@
 
 ### Features
 
-* dev can use debug log configured in core-config.yml ([0e5aaf0](https://github.com/bmadcode/BMAD-METHOD/commit/0e5aaf07bbc6fd9f2706ea26e35f5f38fd72147a))
+* dev can use debug log configured in core-config.yaml ([0e5aaf0](https://github.com/bmadcode/BMAD-METHOD/commit/0e5aaf07bbc6fd9f2706ea26e35f5f38fd72147a))
 
 # [4.8.0](https://github.com/bmadcode/BMAD-METHOD/compare/v4.7.0...v4.8.0) (2025-06-19)
 

package/README.md

@@ -234,7 +234,7 @@ After uploading a bundle, type `/help` to see available commands.
 - **[Complete User Guide](docs/user-guide.md)** - Full walkthrough from project inception to completion
 - **[CLI Commands](docs/user-guide.md#cli-commands)** - Installation, updates, and management
 - **[Upgrading from V3](docs/user-guide.md#upgrading-from-v3-to-v4)** - Migration instructions
-- **[Core Configuration](docs/user-guide.md#core-configuration-coreconfigyml)** - V4's flexible project structure support
+- **[Core Configuration](docs/user-guide.md#core-configuration)** - V4's flexible project structure support
 - **[Teams & Workflows](docs/user-guide.md#team-configurations)** - Pre-configured agent teams
 
 ## Project Structure

package/bmad-core/agents/bmad-master.md

@@ -2,7 +2,7 @@
 
 CRITICAL: Read the full YML to understand your operating params, start activation to alter your state of being, follow startup instructions, stay in this being until told to exit this mode:
 
-```yml
+```yaml
 root: .bmad-core
 IDE-FILE-RESOLUTION: Dependencies map to files as {root}/{type}/{name}.md where root=".bmad-core", type=folder (tasks/templates/checklists/utils), name=dependency name.
 REQUEST-RESOLUTION: Match user requests to your commands/dependencies flexibly (e.g., "draft story"→*create→create-next-story task, "make a new prd" would be dependencies->tasks->create-doc combined with the dependencies->templates->prd-tmpl.md), or ask for clarification if ambiguous.

package/bmad-core/agents/dev.md

@@ -2,7 +2,7 @@
 
 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
 root: .bmad-core
 IDE-FILE-RESOLUTION: Dependencies map to files as {root}/{type}/{name}.md where root=".bmad-core", type=folder (tasks/templates/checklists/utils), name=dependency name.
 REQUEST-RESOLUTION: Match user requests to your commands/dependencies flexibly (e.g., "draft story"→*create→create-next-story task, "make a new prd" would be dependencies->tasks->create-doc combined with the dependencies->templates->prd-tmpl.md), or ask for clarification if ambiguous.
@@ -16,7 +16,7 @@ agent:
 
 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

package/bmad-core/agents/pm.md

@@ -2,7 +2,7 @@
 
 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
 root: .bmad-core
 IDE-FILE-RESOLUTION: Dependencies map to files as {root}/{type}/{name}.md where root=".bmad-core", type=folder (tasks/templates/checklists/utils), name=dependency name.
 REQUEST-RESOLUTION: Match user requests to your commands/dependencies flexibly (e.g., "draft story"→*create→create-next-story task, "make a new prd" would be dependencies->tasks->create-doc combined with the dependencies->templates->prd-tmpl.md), or ask for clarification if ambiguous.

package/bmad-core/agents/po.md

@@ -2,7 +2,7 @@
 
 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
 root: .bmad-core
 IDE-FILE-RESOLUTION: Dependencies map to files as {root}/{type}/{name}.md where root=".bmad-core", type=folder (tasks/templates/checklists/utils), name=dependency name.
 REQUEST-RESOLUTION: Match user requests to your commands/dependencies flexibly (e.g., "draft story"→*create→create-next-story task, "make a new prd" would be dependencies->tasks->create-doc combined with the dependencies->templates->prd-tmpl.md), or ask for clarification if ambiguous.

package/bmad-core/data/bmad-kb.md

@@ -161,11 +161,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:
 
@@ -337,7 +337,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/`)

package/bmad-core/tasks/create-brownfield-story.md

@@ -28,7 +28,7 @@ Create detailed, implementation-ready stories for brownfield projects where trad
 
 #### 0.1 Check Workflow Plan
 
-- Load core-config.yml and check if `workflow.trackProgress: true`
+- Load core-config.yaml and check if `workflow.trackProgress: true`
 - If yes, check for active plan at `workflow.planFile`
 - If plan exists:
   - Verify story creation aligns with current plan step

package/bmad-core/tasks/create-next-story.md

@@ -10,12 +10,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

package/bmad-core/tasks/shard-doc.md

@@ -8,20 +8,20 @@
 
 ## 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."

package/bmad-core/tasks/update-workflow-plan.md

@@ -8,7 +8,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:
 

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

@@ -396,7 +396,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)

package/bmad-core/templates/fullstack-architecture-tmpl.md

@@ -288,7 +288,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:
@@ -644,8 +644,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/

package/bmad-core/utils/plan-management.md

@@ -13,7 +13,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)
 ```
 

package/common/tasks/create-doc.md

@@ -15,7 +15,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:

package/docs/agentic-tools/roo-code-guide.md

@@ -33,7 +33,7 @@ Select mode from the mode selector (usually in status bar):
 ### File Permission Summary
 
 - **Documentation agents** (analyst, pm, po, sm): `.md`, `.txt` only
-- **bmad-architect**: `.md`, `.txt`, `.yml`, `.yaml`, `.json`
+- **bmad-architect**: `.md`, `.txt`, `.yaml`, `.yaml`, `.json`
 - **bmad-qa**: Test files (`.test.*`, `.spec.*`) and `.md`
 - **bmad-ux-expert**: `.md`, `.css`, `.scss`, `.html`, `.jsx`, `.tsx`
 - **Full access**: `bmad-dev`, `bmad-bmad-master`, `bmad-orchestrator`

package/docs/core-architecture.md

@@ -75,12 +75,12 @@ The `.bmad-core` directory contains all the definitions and resources that give
 
 ### 3.2. Agent Teams (`.bmad-core/agent-teams/`)
 
-- **Purpose**: Team files (e.g., `team-all.yml`) 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`.
 
 ### 3.3. Workflows (`.bmad-core/workflows/`)
 
-- **Purpose**: Workflows are YAML files (e.g., `greenfield-fullstack.yml`) 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.
 
 ### 3.4. Reusable Resources (`templates`, `tasks`, `checklists`, `data`)
@@ -239,10 +239,10 @@ bmad-method/
 │   │   ├── sm.md                 # Scrum master agent
 │   │   └── ux-expert.md          # UX designer agent
 │   ├── agent-teams/              # Pre-configured agent teams
-│   │   ├── team-all.yml          # All agents bundle
-│   │   ├── team-fullstack.yml    # Full-stack development team
-│   │   ├── team-ide-minimal.yml  # Minimal IDE-focused team
-│   │   └── team-no-ui.yml        # Backend-only team
+│   │   ├── team-all.yaml         # All agents bundle
+│   │   ├── team-fullstack.yaml   # Full-stack development team
+│   │   ├── team-ide-minimal.yaml # Minimal IDE-focused team
+│   │   └── team-no-ui.yaml       # Backend-only team
 │   ├── checklists/               # Quality assurance checklists
 │   │   ├── architect-checklist.md
 │   │   ├── po-master-checklist.md
@@ -268,11 +268,11 @@ bmad-method/
 │   │   ├── template-format.md    # Template markup spec
 │   │   └── workflow-management.md # Workflow helpers
 │   ├── workflows/                # Development workflows
-│   │   ├── brownfield-enhancement.yml
-│   │   ├── greenfield-fullstack.yml
-│   │   ├── greenfield-service.yml
-│   │   └── greenfield-simple.yml
-│   └── core-config.yml           # V4 configuration system
+│   │   ├── brownfield-enhancement.yaml
+│   │   ├── greenfield-fullstack.yaml
+│   │   ├── greenfield-service.yaml
+│   │   └── greenfield-simple.yaml
+│   └── core-config.yaml          # V4 configuration system
 │
 ├── dist/                         # Pre-built bundles (generated)
 │   ├── agents/                   # Individual agent bundles
@@ -378,7 +378,7 @@ bmad-method/
 
 ### Key Files
 
-- **core-config.yml**: V4's flexible configuration system
+- **core-config.yaml**: V4's flexible configuration system
 - **bmad-kb.md**: Central knowledge base loaded by most agents
 - **template-format.md**: Specification for BMAD's template markup
 - **dependency-resolver.js**: Manages agent resource loading

package/docs/user-guide.md

@@ -104,7 +104,7 @@ After upgrading:
 2. Optionally run the `doc-migration-task` to align your documents with V4 templates - you can do this with your agent by saying something like: 'run {drag in task} against {drag prd or arch file from docs} to align with {drag the template from .bmad-core/templates/full-stack-architecture.md}'
 3. If you have separate front-end and backend architecture docs you can modify step 2 to merge both into a single full stack architecture or separate Front and Back end.
 
-The reason #2 and #3 are optional is because now BMAD V4 makes sharding optional for the SM. See [Core Configuration](#core-configuration-coreconfigyml)
+The reason #2 and #3 are optional is because now BMAD V4 makes sharding optional for the SM. See [Core Configuration](#core-configuration)
 
 **Note**: The agents in `.bmad-core/` fully replace the items in `bmad-agent/` - you can remove the backup folder versions.
 
@@ -456,7 +456,7 @@ The SM agent serves as a critical bridge between high-level planning and technic
 
 When the SM agent executes the `create-next-story` task:
 
-1. **Loads Configuration**: Reads `core-config.yml` to understand project structure
+1. **Loads Configuration**: Reads `core-config.yaml` to understand project structure
 2. **Identifies Next Story**: Sequentially processes stories from epics (1.1, 1.2, 2.1, etc.)
 3. **Gathers Architecture Context**: Reads relevant sharded architecture documents based on story type:
 
@@ -1131,11 +1131,11 @@ This file allows you to define your preferred technologies, patterns, and standa
 
 When creating custom web bundles or uploading to AI platforms, include your `technical-preferences.md` content to ensure agents have your preferences from the start of any conversation.
 
-### Core Configuration (core-config.yml)
+### Core Configuration
 
-The `bmad-core/core-config.yml` file is a critical V4 innovation that enables BMAD to work seamlessly with any project structure, providing maximum flexibility and backwards compatibility.
+The `bmad-core/core-config.yaml` file is a critical V4 innovation that enables BMAD to work seamlessly with any project structure, providing maximum flexibility and backwards compatibility.
 
-#### Understanding core-config.yml
+#### Understanding 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's what makes V4 agents intelligent enough to work with V3 projects, custom layouts, or any document organization you prefer.
 
@@ -1350,7 +1350,7 @@ customTechnicalDocuments:
 1. **Always Configure for Your Structure**: Don't force your project to match BMAD defaults
 2. **Keep devLoadAlwaysFiles Focused**: Only include files needed for every dev task
 3. **Use Debug Log**: Enable when troubleshooting story implementation issues
-4. **Version Control core-config.yml**: Track changes to understand project evolution
+4. **Version Control core-config.yaml**: Track changes to understand project evolution
 5. **Document Custom Patterns**: If using custom epicFilePattern, document it
 
 #### Troubleshooting

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

@@ -286,7 +286,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)
@@ -309,13 +309,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}
@@ -358,7 +358,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:
@@ -494,7 +494,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)
@@ -665,7 +665,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
 
@@ -772,7 +772,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)
@@ -798,7 +798,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)
@@ -1009,7 +1009,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:**
 

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

@@ -150,5 +150,5 @@ workflows: null
 3. Replace all placeholders with actual values
 4. Ensure agent names match available agents in the system
 5. Verify workflow names match available workflows
-6. Save as team-[descriptor].yml or [domain]-team.yml
+6. Save as team-[descriptor].yaml or [domain]-team.yaml
 7. Place in the agent-teams directory of the appropriate location]]

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

@@ -10,7 +10,7 @@
 
 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

package/expansion-packs/bmad-infrastructure-devops/README.md

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

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "bmad-method",
-  "version": "4.24.0",
+  "version": "4.24.1",
   "description": "Breakthrough Method of Agile AI-driven Development",
   "main": "tools/cli.js",
   "bin": {

package/tools/builders/web-builder.js

@@ -1,6 +1,7 @@
 const fs = require("node:fs").promises;
 const path = require("node:path");
 const DependencyResolver = require("../lib/dependency-resolver");
+const yamlUtils = require("../lib/yaml-utils");
 
 class WebBuilder {
   constructor(options = {}) {
@@ -111,10 +112,12 @@ class WebBuilder {
 
   processAgentContent(content) {
     // First, replace content before YAML with the template
+    const yamlContent = yamlUtils.extractYamlFromAgent(content);
+    if (!yamlContent) return content;
+
     const yamlMatch = content.match(/```ya?ml\n([\s\S]*?)\n```/);
     if (!yamlMatch) return content;
-
-    const yamlContent = yamlMatch[1];
+    
     const yamlStartIndex = content.indexOf(yamlMatch[0]);
     const yamlEndIndex = yamlStartIndex + yamlMatch[0].length;
 
@@ -259,7 +262,7 @@ class WebBuilder {
     const agentTeamsDir = path.join(packDir, "agent-teams");
     try {
       const teamFiles = await fs.readdir(agentTeamsDir);
-      const teamFile = teamFiles.find((f) => f.endsWith(".yml"));
+      const teamFile = teamFiles.find((f) => f.endsWith(".yaml"));
 
       if (teamFile) {
         console.log(`    Building team bundle for ${packName}`);
@@ -272,7 +275,7 @@ class WebBuilder {
         for (const outputDir of outputDirs) {
           const teamsOutputDir = path.join(outputDir, "teams");
           await fs.mkdir(teamsOutputDir, { recursive: true });
-          const outputFile = path.join(teamsOutputDir, teamFile.replace(".yml", ".txt"));
+          const outputFile = path.join(teamsOutputDir, teamFile.replace(".yaml", ".txt"));
           await fs.writeFile(outputFile, bundle, "utf8");
           console.log(`    ✓ Created bundle: ${path.relative(this.rootDir, outputFile)}`);
         }
@@ -294,11 +297,11 @@ class WebBuilder {
     sections.push(this.formatSection(`agents#${agentName}`, agentContent));
 
     // Resolve and add agent dependencies
-    const agentYaml = agentContent.match(/```yaml\n([\s\S]*?)\n```/);
-    if (agentYaml) {
+    const yamlContent = yamlUtils.extractYamlFromAgent(agentContent);
+    if (yamlContent) {
       try {
         const yaml = require("js-yaml");
-        const agentConfig = yaml.load(agentYaml[1]);
+        const agentConfig = yaml.load(yamlContent);
 
         if (agentConfig.dependencies) {
           // Add resources, first try expansion pack, then core
@@ -306,7 +309,7 @@ class WebBuilder {
             if (Array.isArray(resources)) {
               for (const resourceName of resources) {
                 let found = false;
-                const extensions = [".md", ".yml", ".yaml"];
+                const extensions = [".md", ".yaml"];
 
                 // Try expansion pack first
                 for (const ext of extensions) {
@@ -391,7 +394,7 @@ class WebBuilder {
 
     // Add team configuration and parse to get agent list
     const teamContent = await fs.readFile(teamConfigPath, "utf8");
-    const teamFileName = path.basename(teamConfigPath, ".yml");
+    const teamFileName = path.basename(teamConfigPath, ".yaml");
     const teamConfig = this.parseYaml(teamContent);
     sections.push(this.formatSection(`agent-teams#${teamFileName}`, teamContent));
 
@@ -416,9 +419,9 @@ class WebBuilder {
       try {
         const resourceFiles = await fs.readdir(resourcePath);
         for (const resourceFile of resourceFiles.filter(
-          (f) => f.endsWith(".md") || f.endsWith(".yml")
+          (f) => f.endsWith(".md") || f.endsWith(".yaml")
         )) {
-          const fileName = resourceFile.replace(/\.(md|yml)$/, "");
+          const fileName = resourceFile.replace(/\.(md|yaml)$/, "");
           expansionResources.set(`${resourceDir}#${fileName}`, true);
         }
       } catch (error) {
@@ -474,13 +477,9 @@ class WebBuilder {
           sections.push(this.formatSection(`agents#${agentId}`, coreAgentContent));
 
           // Parse and collect dependencies from core agent
-          const agentYaml = coreAgentContent.match(/```yaml\n([\s\S]*?)\n```/);
-          if (agentYaml) {
+          const yamlContent = yamlUtils.extractYamlFromAgent(coreAgentContent, true);
+          if (yamlContent) {
             try {
-              // Clean up the YAML to handle command descriptions after dashes
-              let yamlContent = agentYaml[1];
-              yamlContent = yamlContent.replace(/^(\s*-)(\s*"[^"]+")(\s*-\s*.*)$/gm, "$1$2");
-
               const agentConfig = this.parseYaml(yamlContent);
               if (agentConfig.dependencies) {
                 for (const [resourceType, resources] of Object.entries(agentConfig.dependencies)) {
@@ -508,7 +507,7 @@ class WebBuilder {
     // Always prefer expansion pack versions if they exist
     for (const [key, dep] of allDependencies) {
       let found = false;
-      const extensions = [".md", ".yml", ".yaml"];
+      const extensions = [".md", ".yaml"];
 
       // Always check expansion pack first, even if the dependency came from a core agent
       if (expansionResources.has(key)) {
@@ -568,11 +567,11 @@ class WebBuilder {
       try {
         const resourceFiles = await fs.readdir(resourcePath);
         for (const resourceFile of resourceFiles.filter(
-          (f) => f.endsWith(".md") || f.endsWith(".yml")
+          (f) => f.endsWith(".md") || f.endsWith(".yaml")
         )) {
           const filePath = path.join(resourcePath, resourceFile);
           const fileContent = await fs.readFile(filePath, "utf8");
-          const fileName = resourceFile.replace(/\.(md|yml)$/, "");
+          const fileName = resourceFile.replace(/\.(md|yaml)$/, "");
 
           // Only add if not already included as a dependency
           const resourceKey = `${resourceDir}#${fileName}`;

package/tools/bump-all-versions.js

@@ -32,7 +32,7 @@ async function bumpAllVersions() {
   const updatedItems = [];
   
   // First, bump the core version
-  const coreConfigPath = path.join(__dirname, '..', 'bmad-core', 'core-config.yml');
+  const coreConfigPath = path.join(__dirname, '..', 'bmad-core', 'core-config.yaml');
   try {
     const coreConfigContent = fs.readFileSync(coreConfigPath, 'utf8');
     const coreConfig = yaml.load(coreConfigContent);
@@ -59,7 +59,7 @@ async function bumpAllVersions() {
     for (const entry of entries) {
       if (entry.isDirectory() && !entry.name.startsWith('.') && entry.name !== 'README.md') {
         const packId = entry.name;
-        const configPath = path.join(expansionPacksDir, packId, 'config.yml');
+        const configPath = path.join(expansionPacksDir, packId, 'config.yaml');
         
         if (fs.existsSync(configPath)) {
           try {

package/tools/bump-core-version.js

@@ -30,7 +30,7 @@ function bumpVersion(currentVersion, type) {
 
 async function bumpCoreVersion() {
   try {
-    const coreConfigPath = path.join(__dirname, '..', 'bmad-core', 'core-config.yml');
+    const coreConfigPath = path.join(__dirname, '..', 'bmad-core', 'core-config.yaml');
     
     const coreConfigContent = fs.readFileSync(coreConfigPath, 'utf8');
     const coreConfig = yaml.load(coreConfigContent);