fix: update workflow references to gdd module

bmad/_cfg/workflow-manifest.csv

@@ -15,7 +15,6 @@ name,description,module,path,standalone
 "product-brief","Interactive product brief creation workflow that guides users through defining their product vision with multiple input sources and conversational collaboration","bmm","bmad/bmm/workflows/1-analysis/product-brief/workflow.yaml","true"
 "research","Adaptive research workflow supporting multiple research types: market research, deep research prompt generation, technical/architecture evaluation, competitive intelligence, user research, and domain analysis","bmm","bmad/bmm/workflows/1-analysis/research/workflow.yaml","true"
 "create-ux-design","Collaborative UX design facilitation workflow that creates exceptional user experiences through visual exploration and informed decision-making. Unlike template-driven approaches, this workflow facilitates discovery, generates visual options, and collaboratively designs the UX with the user at every step.","bmm","bmad/bmm/workflows/2-plan-workflows/create-ux-design/workflow.yaml","true"
-"gdd","Game Design Document workflow for all game project levels - from small prototypes to full AAA games. Generates comprehensive GDD with game mechanics, systems, progression, and implementation guidance.","bmm","bmad/bmm/workflows/2-plan-workflows/gdd/workflow.yaml","true"
 "narrative","Narrative design workflow for story-driven games and applications. Creates comprehensive narrative documentation including story structure, character arcs, dialogue systems, and narrative implementation guidance.","bmm","bmad/bmm/workflows/2-plan-workflows/narrative/workflow.yaml","true"
 "create-epics-and-stories","Transform PRD requirements into bite-sized stories organized in epics for 200k context dev agents","bmm","bmad/bmm/workflows/2-plan-workflows/prd/create-epics-and-stories/workflow.yaml","true"
 "prd","Unified PRD workflow for BMad Method and Enterprise Method tracks. Produces strategic PRD and tactical epic breakdown. Hands off to architecture workflow for technical design. Note: Quick Flow track uses tech-spec workflow.","bmm","bmad/bmm/workflows/2-plan-workflows/prd/workflow.yaml","true"

bmad/bmm/docs/workflows-analysis.md

@@ -354,7 +354,7 @@ A: No! Analysis is entirely optional. Use only workflows that help you think thr
 A: If unsure, start with `research` (market type) to validate viability, then move to `product-brief` or `game-brief`.
 
 **Q: Can I skip straight to Planning?**
-A: Yes! If you know what you're building and why, skip Phase 1 entirely and start with Phase 2 (prd/gdd/tech-spec).
+A: Yes! If you know what you're building and why, skip Phase 1 entirely and start with Phase 2 (prd/tech-spec).
 
 **Q: How long should Analysis take?**
 A: Typically hours to 1-2 days. If taking longer, you may be over-analyzing. Move to Planning.

bmad/bmm/docs/workflows-planning.md

@@ -188,7 +188,7 @@ The system guides but never forces. You can override recommendations.
 
 **Agent:** PM (orchestrates others as needed)
 
-**Always Use:** This is your planning starting point. Don't call prd/gdd/tech-spec directly unless skipping discovery.
+**Always Use:** This is your planning starting point. Don't call prd/tech-spec directly unless skipping discovery.
 
 **Process:**
 

bmad/bmm/docs/workflows-solutioning.md

@@ -19,7 +19,7 @@ Phase 3 (Solutioning) workflows translate **what** to build (from Planning) into
 ```mermaid
 %%{init: {'theme':'base', 'themeVariables': { 'primaryColor':'#fff','primaryTextColor':'#000','primaryBorderColor':'#000','lineColor':'#000','fontSize':'16px','fontFamily':'arial'}}}%%
 graph TB
-    FromPlanning["<b>FROM Phase 2 Planning</b><br/>PRD/GDD/Tech-Spec complete"]
+    FromPlanning["<b>FROM Phase 2 Planning</b><br/>PRD/Tech-Spec complete"]
 
     subgraph QuickFlow["<b>QUICK FLOW PATH</b>"]
         direction TB