bmad-method 4.23.0 → 4.24.1

package/bmad-core/workflows/{greenfield-ui.yml → greenfield-ui.yaml}

@@ -68,42 +68,92 @@ workflow:
       condition: user_has_generated_ui
       notes: "If user generated UI with v0/Lovable: For polyrepo setup, place downloaded project in separate frontend repo. For monorepo, place in apps/web or frontend/ directory. Review architecture document for specific guidance."
 
+    - agent: po
+      action: shard_documents
+      creates: sharded_docs
+      requires: all_artifacts_in_project
+      notes: |
+        Shard documents for IDE development:
+        - Option A: Use PO agent to shard: @po then ask to shard docs/prd.md
+        - Option B: Manual: Drag shard-doc task + docs/prd.md into chat
+        - Creates docs/prd/ and docs/architecture/ folders with sharded content
+
+    - agent: sm
+      action: create_story
+      creates: story.md
+      requires: sharded_docs
+      repeats: for_each_epic
+      notes: |
+        Story creation cycle:
+        - SM Agent (New Chat): @sm → *create
+        - Creates next story from sharded docs
+        - Story starts in "Draft" status
+
+    - agent: analyst/pm
+      action: review_draft_story
+      updates: story.md
+      requires: story.md
+      optional: true
+      condition: user_wants_story_review
+      notes: |
+        OPTIONAL: Review and approve draft story
+        - NOTE: story-review task coming soon
+        - Review story completeness and alignment
+        - Update story status: Draft → Approved
+
+    - agent: dev
+      action: implement_story
+      creates: implementation_files
+      requires: story.md
+      notes: |
+        Dev Agent (New Chat): @dev
+        - Implements approved story
+        - Updates File List with all changes
+        - Marks story as "Review" when complete
+
+    - agent: qa
+      action: review_implementation
+      updates: implementation_files
+      requires: implementation_files
+      optional: true
+      notes: |
+        OPTIONAL: QA Agent (New Chat): @qa → review-story
+        - Senior dev review with refactoring ability
+        - Fixes small issues directly
+        - Leaves checklist for remaining items
+        - Updates story status (Review → Done or stays Review)
+
+    - agent: dev
+      action: address_qa_feedback
+      updates: implementation_files
+      condition: qa_left_unchecked_items
+      notes: |
+        If QA left unchecked items:
+        - Dev Agent (New Chat): Address remaining items
+        - Return to QA for final approval
+
+    - repeat_development_cycle:
+      action: continue_for_all_stories
+      notes: |
+        Repeat story cycle (SM → Dev → QA) for all epic stories
+        Continue until all stories in PRD are complete
+
+    - agent: po
+      action: epic_retrospective
+      creates: epic-retrospective.md
+      condition: epic_complete
+      optional: true
+      notes: |
+        OPTIONAL: After epic completion
+        - NOTE: epic-retrospective task coming soon
+        - Validate epic was completed correctly
+        - Document learnings and improvements
+
     - workflow_end:
-      action: move_to_ide
+      action: project_complete
       notes: |
-        Planning phase complete! Now transition to IDE Development:
-        
-        1. ENSURE DOCUMENTS ARE IN PROJECT:
-           - Copy final prd.md to project's docs/prd.md
-           - Copy final architecture.md to project's docs/architecture.md
-           - All documents must be in the project before proceeding
-        
-        2. SHARD DOCUMENTS (in IDE):
-           - Option A: Use PO agent to shard: @po then ask to shard docs/prd.md
-           - Option B: Manual: Drag shard-doc task + docs/prd.md into chat
-           - This creates docs/prd/ and docs/architecture/ folders with sharded content
-        
-        3. START DEVELOPMENT CYCLE:
-           a. SM Agent (New Chat): @sm → *create
-              - Creates next story from sharded docs
-              - Review and approve story (Draft → Approved)
-           
-           b. Dev Agent (New Chat): @dev
-              - Implements approved story
-              - Updates File List with all changes
-              - Marks story as "Review" when complete
-           
-           c. QA Agent (New Chat): @qa → review-story
-              - Senior dev review with refactoring ability
-              - Fixes small issues directly
-              - Leaves checklist for remaining items
-              - Updates story status (Review → Done or stays Review)
-           
-           d. If QA left unchecked items:
-              - Dev Agent (New Chat): Address remaining items
-              - Return to QA for final approval
-        
-        4. REPEAT: Continue cycle for all epic stories
+        All stories implemented and reviewed!
+        Project development phase complete.
         
         Reference: data#bmad-kb:IDE Development Workflow
 
@@ -124,21 +174,45 @@ workflow:
         G --> H
         H --> I{PO finds issues?}
         I -->|Yes| J[Return to relevant agent for fixes]
-        I -->|No| K[Move to IDE Environment]
+        I -->|No| K[po: shard documents]
         J --> H
+        
+        K --> L[sm: create story]
+        L --> M{Review draft story?}
+        M -->|Yes| N[analyst/pm: review & approve story]
+        M -->|No| O[dev: implement story]
+        N --> O
+        O --> P{QA review?}
+        P -->|Yes| Q[qa: review implementation]
+        P -->|No| R{More stories?}
+        Q --> S{QA found issues?}
+        S -->|Yes| T[dev: address QA feedback]
+        S -->|No| R
+        T --> Q
+        R -->|Yes| L
+        R -->|No| U{Epic retrospective?}
+        U -->|Yes| V[po: epic retrospective]
+        U -->|No| W[Project Complete]
+        V --> W
 
         B -.-> B1[Optional: brainstorming]
         B -.-> B2[Optional: market research]
         D -.-> D1[Optional: user research]
         E -.-> E1[Optional: technical research]
 
-        style K fill:#90EE90
+        style W fill:#90EE90
+        style K fill:#ADD8E6
+        style L fill:#ADD8E6
+        style O fill:#ADD8E6
         style D3 fill:#E6E6FA
         style D4 fill:#E6E6FA
         style B fill:#FFE4B5
         style C fill:#FFE4B5
         style D fill:#FFE4B5
         style E fill:#FFE4B5
+        style N fill:#F0E68C
+        style Q fill:#F0E68C
+        style V fill:#F0E68C
     ```
 
   decision_guidance:

package/common/tasks/create-doc.md

@@ -13,11 +13,22 @@ Generate documents from templates by EXECUTING (not just reading) embedded instr
 
 ## Execution Flow
 
+### 0. Check Workflow Plan (if configured)
+
+[[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:
+  - Verify this is the expected next step
+  - If out of sequence and `enforceSequence: true`, warn user and halt without user override
+  - If out of sequence and `enforceSequence: false`, ask for confirmation
+- Continue with normal execution after plan check
+
 ### 1. Identify Template
 
 - Load from `templates#*` or `{root}/templates directory`
 - Agent-specific templates are listed in agent's dependencies
-- If agent has `templates: [prd-tmpl, architecture-tmpl]`, offer to create "PRD" and "Architecture" documents
+- If agent has `templates: [prd-tmpl, architecture-tmpl]` for example, then offer to create "PRD" and "Architecture" documents
 
 ### 2. Ask Interaction Mode
 
@@ -54,6 +65,15 @@ Generate documents from templates by EXECUTING (not just reading) embedded instr
 - Begin directly with content (no preamble)
 - Include any handoff prompts from template
 
+### 6. Update Workflow Plan (if applicable)
+
+[[LLM: After successful document creation]]
+
+- If plan tracking is enabled and document was part of plan:
+  - Call update-workflow-plan task to mark step complete
+  - Parameters: task: create-doc, step_id: {from plan}, status: complete
+  - Show next recommended step from plan
+
 ## Common Mistakes to Avoid
 
 ❌ Skipping elicitation tasks

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.23.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);

package/tools/bump-expansion-version.js

@@ -38,7 +38,7 @@ function bumpVersion(currentVersion, type) {
 
 async function updateVersion() {
   try {
-    const configPath = path.join(__dirname, '..', 'expansion-packs', packId, 'config.yml');
+    const configPath = path.join(__dirname, '..', 'expansion-packs', packId, 'config.yaml');
     
     if (!fs.existsSync(configPath)) {
       console.error(`Error: Expansion pack '${packId}' not found`);

package/tools/installer/README.md

@@ -16,7 +16,7 @@ installer/
 │   ├── ide-setup.js     # IDE-specific setup
 │   └── prompts.js       # Interactive CLI prompts
 ├── config/          # Configuration files
-│   └── install.config.yml # Installation profiles
+│   └── install.config.yaml # Installation profiles
 ├── templates/       # IDE template files
 │   ├── cursor-rules.md     # Cursor template
 │   ├── claude-commands.md  # Claude Code template

package/tools/installer/bin/bmad.js

@@ -158,7 +158,7 @@ async function promptInstallation() {
   const choices = [];
   
   // Load core config to get short-title
-  const coreConfigPath = path.join(__dirname, '..', '..', '..', 'bmad-core', 'core-config.yml');
+  const coreConfigPath = path.join(__dirname, '..', '..', '..', 'bmad-core', 'core-config.yaml');
   const coreConfig = yaml.load(await fs.readFile(coreConfigPath, 'utf8'));
   const coreShortTitle = coreConfig['short-title'] || 'BMad Agile Core System';
   
@@ -166,7 +166,7 @@ async function promptInstallation() {
   let bmadOptionText;
   if (state.type === 'v4_existing') {
     const currentVersion = state.manifest?.version || 'unknown';
-    const newVersion = coreConfig.version || 'unknown'; // Use version from core-config.yml
+    const newVersion = coreConfig.version || 'unknown'; // Use version from core-config.yaml
     const versionInfo = currentVersion === newVersion 
       ? `(v${currentVersion} - reinstall)`
       : `(v${currentVersion} → v${newVersion})`;