Fixing config.yaml, editing README.md to indicate correct workflow

expansion-packs/bmad-godot-game-dev/README.md

@@ -24,11 +24,13 @@ graph TD
     G -->|No| E2["Game-Designer: Interactive GDD Creation (More Questions)"]
     E --> F["GDD Created with FRs, NFRs, Epics & Stories"]
     E2 --> F
-    F["Game-Architect: Create GameArchitecture from GDD"] --> I["PO: Run game-po-validation-checklist"]
+    F --> F2["Game-PM: Create PRD from GDD"]
+    F2 --> F3["Game-Architect: Create Game Architecture from GDD and PRD"]
+    F3 --> I["PO: Run game-po-validation-checklist"]
     I --> J{"Documents Aligned?"}
     J -->|Yes| K["Planning Complete"]
     J -->|No| L["Game-Designer: Update Epics & Stories"]
-    L --> M["Update GDD/GameArchitecture as needed"]
+    L --> M["Update GDD/Game Architecture as needed"]
     M --> I
     K --> N["📁 Switch to IDE (If in a Web Agent Platform)"]
     N --> O["Game-PO: Shard Documents"]
@@ -44,8 +46,7 @@ graph TD
     style E2 fill:#fff3e0,color:#000
     style F fill:#fff3e0,color:#000
     style F2 fill:#e3f2fd,color:#000
-    style F3 fill:#e1f5fe,color:#000
+    style F3 fill:#f3e5f5,color:#000
-    style F4 fill:#e1f5fe,color:#000
     style G fill:#e3f2fd,color:#000
     style H fill:#f3e5f5,color:#000
     style H2 fill:#f3e5f5,color:#000

expansion-packs/bmad-godot-game-dev/agents/bmad-orchestrator.md

@@ -19,7 +19,7 @@ REQUEST-RESOLUTION: Match user requests to your commands/dependencies flexibly (
 activation-instructions:
   - STEP 1: Read THIS ENTIRE FILE - it contains your complete persona definition
   - STEP 2: Adopt the persona defined in the 'agent' and 'persona' sections below
-  - STEP 3: Load and read `bmad-core/core-config.yaml` (project configuration) before any greeting
+  - STEP 3: Load and read `.bmad-godot-game-dev/config.yaml` (project configuration) before any greeting
   - STEP 4: Greet user with your name/role and immediately run `*help` to display available commands
   - DO NOT: Load any other agent files during activation
   - ONLY load dependency files when user selects them for execution via command or request of a task

expansion-packs/bmad-godot-game-dev/agents/game-analyst.md

@@ -19,7 +19,7 @@ REQUEST-RESOLUTION: Match user requests to your commands/dependencies flexibly (
 activation-instructions:
   - STEP 1: Read THIS ENTIRE FILE - it contains your complete persona definition
   - STEP 2: Adopt the persona defined in the 'agent' and 'persona' sections below
-  - STEP 3: Load and read `.bmad-godot-game-dev/core-config.yaml` (project configuration) before any greeting
+  - STEP 3: Load and read `.bmad-godot-game-dev/config.yaml` (project configuration) before any greeting
   - STEP 4: Greet user with your name/role and immediately run `*help` to display available commands
   - DO NOT: Load any other agent files during activation
   - ONLY load dependency files when user selects them for execution via command or request of a task

expansion-packs/bmad-godot-game-dev/agents/game-architect.md

@@ -17,7 +17,7 @@ REQUEST-RESOLUTION: Match user requests to your commands/dependencies flexibly (
 activation-instructions:
   - STEP 1: Read THIS ENTIRE FILE - it contains your complete persona definition
   - STEP 2: Adopt the persona defined in the 'agent' and 'persona' sections below
-  - STEP 3: Load and read `.bmad-godot-game-dev/core-config.yaml` (project configuration) before any greeting
+  - STEP 3: Load and read `.bmad-godot-game-dev/config.yaml` (project configuration) before any greeting
   - STEP 4: Greet user with your name/role and immediately run `*help` to display available commands
   - DO NOT: Load any other agent files during activation
   - ONLY load dependency files when user selects them for execution via command or request of a task

expansion-packs/bmad-godot-game-dev/agents/game-designer.md

@@ -17,7 +17,7 @@ REQUEST-RESOLUTION: Match user requests to your commands/dependencies flexibly (
 activation-instructions:
   - STEP 1: Read THIS ENTIRE FILE - it contains your complete persona definition
   - STEP 2: Adopt the persona defined in the 'agent' and 'persona' sections below
-  - STEP 3: Load and read `.bmad-godot-game-dev/core-config.yaml` (project configuration) before any greeting
+  - STEP 3: Load and read `.bmad-godot-game-dev/config.yaml` (project configuration) before any greeting
   - STEP 4: Greet user with your name/role and immediately run `*help` to display available commands
   - DO NOT: Load any other agent files during activation
   - ONLY load dependency files when user selects them for execution via command or request of a task

expansion-packs/bmad-godot-game-dev/agents/game-developer.md

@@ -17,7 +17,7 @@ REQUEST-RESOLUTION: Match user requests to your commands/dependencies flexibly (
 activation-instructions:
   - STEP 1: Read THIS ENTIRE FILE - it contains your complete persona definition
   - STEP 2: Adopt the persona defined in the 'agent' and 'persona' sections below
-  - STEP 3: Load and read `.bmad-godot-game-dev/core-config.yaml` (project configuration) before any greeting
+  - STEP 3: Load and read `.bmad-godot-game-dev/config.yaml` (project configuration) before any greeting
   - STEP 4: Greet user with your name/role and immediately run `*help` to display available commands
   - DO NOT: Load any other agent files during activation
   - ONLY load dependency files when user selects them for execution via command or request of a task

expansion-packs/bmad-godot-game-dev/agents/game-pm.md

@@ -17,7 +17,7 @@ REQUEST-RESOLUTION: Match user requests to your commands/dependencies flexibly (
 activation-instructions:
   - STEP 1: Read THIS ENTIRE FILE - it contains your complete persona definition
   - STEP 2: Adopt the persona defined in the 'agent' and 'persona' sections below
-  - STEP 3: Load and read `.bmad-godot-game-dev/core-config.yaml` (project configuration) before any greeting
+  - STEP 3: Load and read `.bmad-godot-game-dev/config.yaml` (project configuration) before any greeting
   - STEP 4: Greet user with your name/role and immediately run `*help` to display available commands
   - DO NOT: Load any other agent files during activation
   - ONLY load dependency files when user selects them for execution via command or request of a task

expansion-packs/bmad-godot-game-dev/agents/game-po.md

@@ -17,7 +17,7 @@ REQUEST-RESOLUTION: Match user requests to your commands/dependencies flexibly (
 activation-instructions:
   - STEP 1: Read THIS ENTIRE FILE - it contains your complete persona definition
   - STEP 2: Adopt the persona defined in the 'agent' and 'persona' sections below
-  - STEP 3: Load and read `.bmad-godot-game-dev/core-config.yaml` (project configuration) before any greeting
+  - STEP 3: Load and read `.bmad-godot-game-dev/config.yaml` (project configuration) before any greeting
   - STEP 4: Greet user with your name/role and immediately run `*help` to display available commands
   - DO NOT: Load any other agent files during activation
   - ONLY load dependency files when user selects them for execution via command or request of a task

expansion-packs/bmad-godot-game-dev/agents/game-qa.md

@@ -17,7 +17,7 @@ REQUEST-RESOLUTION: Match user requests to your commands/dependencies flexibly (
 activation-instructions:
   - STEP 1: Read THIS ENTIRE FILE - it contains your complete persona definition
   - STEP 2: Adopt the persona defined in the 'agent' and 'persona' sections below
-  - STEP 3: Load and read `.bmad-godot-game-dev/core-config.yaml` (project configuration) before any greeting
+  - STEP 3: Load and read `.bmad-godot-game-dev/config.yaml` (project configuration) before any greeting
   - STEP 4: Greet user with your name/role and immediately run `*help` to display available commands
   - DO NOT: Load any other agent files during activation
   - ONLY load dependency files when user selects them for execution via command or request of a task

expansion-packs/bmad-godot-game-dev/agents/game-sm.md

@@ -17,7 +17,7 @@ REQUEST-RESOLUTION: Match user requests to your commands/dependencies flexibly (
 activation-instructions:
   - STEP 1: Read THIS ENTIRE FILE - it contains your complete persona definition
   - STEP 2: Adopt the persona defined in the 'agent' and 'persona' sections below
-  - STEP 3: Load and read `.bmad-godot-game-dev/core-config.yaml` (project configuration) before any greeting
+  - STEP 3: Load and read `.bmad-godot-game-dev/config.yaml` (project configuration) before any greeting
   - STEP 4: Greet user with your name/role and immediately run `*help` to display available commands
   - DO NOT: Load any other agent files during activation
   - ONLY load dependency files when user selects them for execution via command or request of a task

expansion-packs/bmad-godot-game-dev/agents/game-ux-expert.md

@@ -17,7 +17,7 @@ REQUEST-RESOLUTION: Match user requests to your commands/dependencies flexibly (
 activation-instructions:
   - STEP 1: Read THIS ENTIRE FILE - it contains your complete persona definition
   - STEP 2: Adopt the persona defined in the 'agent' and 'persona' sections below
-  - STEP 3: Load and read `.bmad-godot-game-dev/core-config.yaml` (project configuration) before any greeting
+  - STEP 3: Load and read `.bmad-godot-game-dev/config.yaml` (project configuration) before any greeting
   - STEP 4: Greet user with your name/role and immediately run `*help` to display available commands
   - DO NOT: Load any other agent files during activation
   - ONLY load dependency files when user selects them for execution via command or request of a task

expansion-packs/bmad-godot-game-dev/config.yaml

@@ -4,3 +4,24 @@ short-title: Godot Game Dev Pack
 description: Game Development expansion pack for BMad Method - Godot GDscript & C# focused
 author: sjennings (Lum), based on BMAD Unity Game Dev expansion pack by pbean (PinkyD)
 slashPrefix: BmadG
+markdownExploder: true
+qa:
+  qaLocation: docs/qa
+prd:
+  prdFile: docs/prd.md
+  prdVersion: v4
+  prdSharded: true
+  prdShardedLocation: docs/prd
+  epicFilePattern: epic-{n}*.md
+architecture:
+  architectureFile: docs/architecture.md
+  architectureVersion: v4
+  architectureSharded: true
+  architectureShardedLocation: docs/architecture
+customTechnicalDocuments: null
+devLoadAlwaysFiles:
+  - docs/architecture/coding-standards.md
+  - docs/architecture/tech-stack.md
+  - docs/architecture/source-tree.md
+devDebugLog: .ai/debug-log.md
+devStoryLocation: docs/stories

expansion-packs/bmad-godot-game-dev/data/bmad-kb.md

@@ -156,7 +156,7 @@ npx bmad-method install
 - Game story management and implementation workflow
 - Godot testing with GUT/GoDotTest, profiling, and debugging
 
-**Cost-Saving Tip for Game Development**: Create large game design documents in web UI, then copy to `docs/game-design-doc.md` and `docs/game-architecture.md` in your Godot project before switching to IDE for development.
+**Cost-Saving Tip for Game Development**: Create large game design documents in web UI, then copy to `docs/game-design-doc.md` and `docs/architecture.md` in your Godot project before switching to IDE for development.
 
 ### IDE-Only Game Development Workflow Considerations
 
@@ -214,9 +214,9 @@ gdd:
 gamearchitecture:
   gamearchitectureFile: docs/architecture.md
   gamearchitectureVersion: v3
-  gamearchitectureLocation: docs/game-architecture.md
+  gamearchitectureLocation: docs/architecture.md
   gamearchitectureSharded: true
-  gamearchitectureShardedLocation: docs/game-architecture
+  gamearchitectureShardedLocation: docs/architecture
 gamebriefdocLocation: docs/game-brief.md
 levelDesignLocation: docs/level-design.md
 # Specify Godot executable location if needed
@@ -227,9 +227,9 @@ devStoryLocation: docs/stories
 slashPrefix: BmadG
 # Sharded architecture files for developer reference
 devLoadAlwaysFiles:
-  - docs/game-architecture/9-coding-standards.md
+  - docs/architecture/9-coding-standards.md
-  - docs/game-architecture/3-tech-stack.md
+  - docs/architecture/3-tech-stack.md
-  - docs/game-architecture/8-godot-project-structure.md
+  - docs/architecture/8-godot-project-structure.md
 ```
 
 ## Complete Game Development Workflow
@@ -245,7 +245,7 @@ devLoadAlwaysFiles:
 3. **Game Design Document Creation**: `/bmadg/game-designer` - Use `game-design-doc-tmpl` for comprehensive game requirements
 4. **Game Architecture Design**: `/bmadg/game-architect` - Use `game-architecture-tmpl` for Godot technical foundation
 5. **Level Design Framework**: `/bmadg/game-designer` - Use `level-design-doc-tmpl` for level structure planning
-6. **Document Preparation**: Copy final documents to Godot project as `docs/game-design-doc.md`, `docs/game-brief.md`, `docs/level-design.md` and `docs/game-architecture.md`
+6. **Document Preparation**: Copy final documents to Godot project as `docs/game-design-doc.md`, `docs/game-brief.md`, `docs/level-design.md` and `docs/architecture.md`
 
 #### Example Game Planning Prompts
 
@@ -270,7 +270,7 @@ Consider both GDScript and C# for appropriate systems."
 
 - **Why**: Godot development workflow requires scene operations, GDScript/C# coding, and real-time testing
 - **Cost Benefit**: Web UI is more cost-effective for large game design creation; IDE is optimized for Godot development
-- **Required Files**: Ensure `docs/game-design-doc.md` and `docs/game-architecture.md` exist in your Godot project
+- **Required Files**: Ensure `docs/game-design-doc.md` and `docs/architecture.md` exist in your Godot project
 
 ### Godot IDE Development Workflow
 
@@ -282,7 +282,7 @@ Consider both GDScript and C# for appropriate systems."
      a) **Manual**: Use core BMad `shard-doc` task if available
      b) **Agent**: Ask core `@bmad-master` agent to shard documents
    - Shards `docs/game-design-doc.md` → `docs/game-design/` folder
-   - Shards `docs/game-architecture.md` → `docs/game-architecture/` folder
+   - Shards `docs/architecture.md` → `docs/architecture/` folder
    - **WARNING**: Do NOT shard in Web UI - copying many small files to Godot is painful!
 
 2. **Verify Sharded Game Content**:
@@ -293,7 +293,7 @@ Consider both GDScript and C# for appropriate systems."
 Resulting Godot Project Folder Structure:
 
 - `docs/game-design/` - Broken down game design sections
-- `docs/game-architecture/` - Broken down Godot architecture sections
+- `docs/architecture/` - Broken down Godot architecture sections
 - `docs/game-stories/` - Generated game development stories
 
 3. **Game Development Cycle** (Sequential, one game story at a time):
@@ -387,7 +387,7 @@ Each status change requires user verification and approval before proceeding.
 ### Required File Naming for Game Framework Integration
 
 - `docs/game-design-doc.md` - Game Design Document
-- `docs/game-architecture.md` - Godot System Architecture Document
+- `docs/architecture.md` - Godot System Architecture Document
 
 **Why These Names Matter for Game Development**:
 
@@ -401,7 +401,7 @@ Each status change requires user verification and approval before proceeding.
 
 1. **Use Web UI**: Create game documents in web interface for cost efficiency
 2. **Copy Final Output**: Save complete markdown to your Godot project
-3. **Standard Names**: Save as `docs/game-design-doc.md` and `docs/game-architecture.md`
+3. **Standard Names**: Save as `docs/game-design-doc.md` and `docs/architecture.md`
 4. **Switch to Godot IDE**: Use IDE agents for Godot development and smaller game documents
 
 ### Game Document Sharding