feat: Add documentation guides, simplify folder structure, and major workflow refactoring

Created two comprehensive guides for v6 features:

**docs/agent-customization-guide.md**
- Complete guide for customizing agent names, personas, memories, and behaviors
- Update-safe customization via bmad/_cfg/agents/ configuration files
- Real-world examples (TDD setup, multilingual agents, custom workflows)
- Troubleshooting and best practices

**docs/web-bundles-gemini-gpt-guide.md**
- Comprehensive guide for using BMad agents in Gemini Gems and Custom GPTs
- Critical setup rules with exact configuration text required
- Cost-saving strategy: web planning → local implementation (60-80% savings)
- Platform comparison (Gemini Gems strongly recommended over Custom GPTs)
- Complete workflow examples showing full planning-to-implementation cycle
- Team bundle guidance (Gemini 2.5 Pro+ only)

**README.md updates**
- Added prominent links in v6 Core Enhancements section
- Created new "Customization & Sharing" documentation category
- Web Bundles feature highlighted with direct guide link

**Unified output folder structure across all modules:**

**Before (confusing):**
- output_folder: Main docs
- game_design_docs: Separate design folder
- tech_docs: Separate technical folder
- dev_ephemeral_location: Separate ephemeral folder outside docs

**After (simplified):**
- output_folder: Single location for ALL AI-generated artifacts (default: "docs")
  - Clearer prompt: "Where should AI Generated Artifacts be saved?"
- sprint_artifacts: Phase 4 ephemeral content now WITHIN output_folder
  - BMM: {output_folder}/stories (stories, context, reports)
  - BMGD: {output_folder}/sprint-artifacts
  - No longer in separate {bmad_folder}-ephemeral location

**Benefits:**
- One clear location for all planning artifacts (PRD, Architecture, UX, etc.)
- Phase 4 ephemeral items logically grouped within output folder
- Eliminated confusing separate folder proliferation
- sprint_artifacts now configurable per module

**Files changed:**
- src/core/_module-installer/install-config.yaml
- src/modules/bmm/_module-installer/install-config.yaml
- src/modules/bmgd/_module-installer/install-config.yaml

**Also cleaned up BMGD config:**
- Renamed: specified_framework → primary_platform (clearer naming)
- Removed: unused data_path variable

Replaced old "project_level" (0-4) system with new "selected_track" terminology:
- **quick-flow**: Bug fixes and small features (replaces Level 0-1)
- **bmad-method**: Full planning track (replaces Level 2-3)
- **enterprise-bmad-method**: Extended planning (replaces Level 4)

**Core workflow updates:**
- solutioning-gate-check: Complete rewrite of validation logic for track-based artifacts
- architecture: Updated context detection, error handling, and messaging for tracks
- workflow-init: Updated artifact detection patterns for track-based paths
- All workflow status paths updated (method-greenfield, method-brownfield, enterprise-*)

Unified variable naming conventions across all workflows:
- {output_folder} → {output-folder} (hyphenated format)
- {dev_ephemeral_location} → {sprint_artifacts} (clearer purpose)
- Hardcoded status file paths → {workflow_status_file} variable

Fixed corrupted variable patterns throughout workflow files:
- {output*folder} → {output-folder}
- {ephemeral*location} → {sprint_artifacts}
- \_prd* → *prd* (escaped underscore artifacts)
- **\*\***\_\_\_**\*\*** → proper field placeholders

Affected patterns included malformed glob patterns, template variables, and markdown formatting artifacts from previous edits.

**Architecture workflow (create-architecture):**
- Fixed: "Decision Architecture" → "Create Architecture" (consistent naming)
- Improved PRD not found handling with exit/continue options
- Better user guidance when running standalone vs. within workflow path
- Removed hardcoded Level checks, now track-aware
- Enhanced validation checklist formatting (□ → - [])
- Typo fixes: "mulitple" → "multiple"

**Solutioning gate check:**
- Complete validation logic rewrite for track-based system
- Removed Level-specific artifact expectations
- Simplified document discovery (track determines what exists)
- Better analysis prompts and user feedback

**Workflow-init:**
- Updated artifact detection patterns for new folder structure
- Fixed corrupt glob patterns throughout
- Better sprint_artifacts location detection
- Improved workflow path assignment logic

**Various workflows:**
- Consistent variable naming across 40+ workflow files
- Improved error messages and user guidance
- Better markdown formatting (checkboxes, lists)
- Removed redundant validation criteria files (now inline)

Removed duplicate BMGD 4-production workflows (12 workflows):
- code-review, correct-course, create-story, dev-story
- epic-tech-context, retrospective, sprint-planning
- story-context, story-done, story-ready

**Why:** BMGD now uses shared BMM Phase 4 implementation workflows
**Benefit:** Single source of truth, no duplication to maintain

Also removed:
- validation-criteria.yaml (validation now inline in instructions)
- architecture-patterns.yaml references (patterns now managed differently)
- AUDIT-REPORT.md files (stale audit artifacts)

**BMB workflows:**
- Updated checklists for workflow and module creation
- Improved agent architecture documentation
- Minor instruction clarifications

**Core brainstorming workflow:**
- Updated README with usage examples
- Enhanced instructions and template clarity
- Better integration with other modules

**BMM installer:**
- Updated for track-based system
- sprint_artifacts configuration

**Tech Writer agent:**
- Minor configuration update for documentation workflows

Removed 200+ files that should not be in repository:
- Installed agent markdown files (analyst, architect, dev, pm, sm, tea, etc.)
- Complete workflow instruction copies
- Documentation duplicates (quick-start, agents-guide, workflows-*)
- Test architecture knowledge base (22 files, 14,000+ lines)
- Configuration files (config.yaml, team definitions)

These are generated during installation and should not be version controlled.

Removed 21 pre-generated XML bundles:
- BMM agents (analyst, architect, dev, pm, sm, tea, tech-writer, ux-designer)
- BMGD agents (game-architect, game-designer, game-dev, game-scrum-master)
- CIS agents (brainstorming-coach, creative-problem-solver, etc.)
- Team bundles (team-fullstack, team-gamedev, creative-squad)

**Why:** Users should generate fresh bundles via `npm run bundle` to get latest changes and customizations.

- **2 new documentation files** (comprehensive guides)
- **98 source files modified** (299 insertions, 6,567 deletions)
- **3 installer config files simplified** (major folder structure improvement)
- **200+ .bmad/ artifacts removed** (should not be in repo)
- **21 web-bundle files removed** (users regenerate as needed)
- **12 duplicate workflows removed** (BMGD consolidation)
- **40+ workflows updated** (track system, variable standardization, corruption fixes)

src/modules/bmm/workflows/3-solutioning/architecture/architecture-patterns.yaml

@@ -319,29 +319,3 @@ decision_rules:
       - quick_prototype: "Railway"
       - global_edge: "Fly.io"
       - kubernetes_needed: "GCP or AWS EKS"
-
-# Anti-patterns to avoid
-anti_patterns:
-  overengineering:
-    signs:
-      - "Microservices for < 10k users"
-      - "Kubernetes for single app"
-      - "GraphQL for 5 endpoints"
-      - "Event sourcing for CRUD app"
-    recommendation: "Start simple, evolve as needed"
-
-  underengineering:
-    signs:
-      - "No authentication strategy"
-      - "No error handling plan"
-      - "No monitoring approach"
-      - "No backup strategy"
-    recommendation: "Cover the fundamentals"
-
-  technology_soup:
-    signs:
-      - "5+ different databases"
-      - "Multiple frontend frameworks"
-      - "Inconsistent patterns"
-      - "Too many languages"
-    recommendation: "Maintain consistency"

src/modules/bmm/workflows/3-solutioning/architecture/checklist.md

@@ -225,19 +225,15 @@
 
 ### Critical Issues Found
 
-- [ ] Issue 1: **\*\***\_\_\_**\*\***
-- [ ] Issue 2: **\*\***\_\_\_**\*\***
-- [ ] Issue 3: **\*\***\_\_\_**\*\***
+<!-- replace with list of critical issues found, or N/A -->
 
 ### Recommended Actions Before Implementation
 
-1. ***
-2. ***
-3. ***
+<!-- replace with list of recommended actions, or N/A -->
 
 ---
 
-**Next Step**: Run the **solutioning-gate-check** workflow to validate alignment between PRD, Architecture, and Stories before beginning implementation.
+**Next Step**: Run the **solutioning-gate-check** workflow to validate alignment between PRD, UX, Architecture, and Stories before beginning implementation.
 
 ---
 

src/modules/bmm/workflows/3-solutioning/architecture/instructions.md

@@ -16,7 +16,7 @@
 <action>Check if {output_folder}/bmm-workflow-status.yaml exists</action>
 
 <check if="status file not found">
-  <output>No workflow status file found. Decision Architecture can run standalone or as part of BMM workflow path.</output>
+  <output>No workflow status file found. Create Architecture can run standalone or as part of BMM workflow path.</output>
   <output>**Recommended:** Run `workflow-init` first for project context tracking and workflow sequencing.</output>
   <ask>Continue in standalone mode or exit to run workflow-init? (continue/exit)</ask>
   <check if="continue">
@@ -33,17 +33,9 @@
   <action>Check status of "create-architecture" workflow</action>
   <action>Get project_level from YAML metadata</action>
   <action>Find first non-completed workflow (next expected workflow)</action>
-
-  <check if="project_level < 3">
-    <output>**Note: Level {{project_level}} Project**
-
-The Detailed Architecture is typically for Level 3-4 projects, but can be used for any project that needs architectural planning.
-
-For Level {{project_level}}, we'll keep the architecture appropriately scoped.
-</output>
 </check>
 
-  <check if="create-architecture status is file path (already completed)">
+  <check if="create-architecture status is indicates already completed">
     <output>⚠️ Architecture already completed: {{create-architecture status}}</output>
     <ask>Re-running will overwrite the existing architecture. Continue? (y/n)</ask>
     <check if="n">
@@ -62,7 +54,6 @@ For Level {{project_level}}, we'll keep the architecture appropriately scoped.
   </check>
 
 <action>Set standalone_mode = false</action>
-</check>
 
 <action>Check for existing PRD and epics files using fuzzy matching</action>
 
@@ -70,21 +61,22 @@ For Level {{project_level}}, we'll keep the architecture appropriately scoped.
 <check if="PRD_not_found">
 <output>**PRD Not Found**
 
-Decision Architecture works from your Product Requirements Document (PRD).
+Creation of an Architecture works from your Product Requirements Document (PRD), along with an optional UX Design and other assets.
 
-Looking for: _PRD_, PRD.md, or prd/index.md + files in {output_folder}
+Looking for: _prd_.md, or prd/\* + files in {output_folder}
 
-Please run the PRD workflow first to define your requirements.
-
-Architect: `create-prd`
+Please talk to the PM Agent to run the Create PRD workflow first to define your requirements, or if I am mistaken and it does exist, provide the file now.
 </output>
-<action>Exit workflow - PRD required</action>
+<ask>Would you like to exit, or can you provide a PRD?
+<action if='yes to exit'>Exit workflow - PRD required</action>
+<action if='prd provided'>Proceed to Step 1</action>
+</ask>
 </check>
 
 </step>
 
 <step n="1" goal="Load and understand project context">
-  <action>Load the PRD using fuzzy matching: {prd_file}, if the PRD is mulitple files in a folder, load the index file and all files associated with the PRD</action>
+  <action>Load the PRD using fuzzy matching: {prd_file}, if the PRD is multiple files in a folder, load the index file and all files associated with the PRD</action>
   <action>Load epics file using fuzzy matching: {epics_file}</action>
 
 <action>Check for UX specification using fuzzy matching:
@@ -623,14 +615,15 @@ Enforcement: "All agents MUST follow this pattern"
 <action>Run validation checklist from {installed_path}/checklist.md</action>
 
 <action>Verify MANDATORY items:
-□ Decision table has Version column with specific versions
-□ Every epic is mapped to architecture components
-□ Source tree is complete, not generic
-□ No placeholder text remains
-□ All FRs from PRD have architectural support
-□ All NFRs from PRD are addressed
-□ Implementation patterns cover all potential conflicts
-□ Novel patterns are fully documented (if applicable)
+
+- [] Decision table has Version column with specific versions
+- [] Every epic is mapped to architecture components
+- [] Source tree is complete, not generic
+- [] No placeholder text remains
+- [] All FRs from PRD have architectural support
+- [] All NFRs from PRD are addressed
+- [] Implementation patterns cover all potential conflicts
+- [] Novel patterns are fully documented (if applicable)
 </action>
 
   <check if="validation_failed">

src/modules/bmm/workflows/3-solutioning/architecture/workflow.yaml

@@ -12,29 +12,20 @@ document_output_language: "{config_source}:document_output_language"
 user_skill_level: "{config_source}:user_skill_level"
 date: system-generated
 
-# Input requirements - We work from PRD, Epics, and optionally UX Spec
-recommended_inputs:
-  - prd: "Product Requirements Document with FRs and NFRs"
-  - epics: "Epic definitions with user stories and acceptance criteria"
-  - ux_spec: "UX specification with interface designs and interaction patterns (optional)"
-
 # Smart input file references - handles both whole docs and sharded docs
 # Priority: Whole document first, then sharded version
 input_file_patterns:
   prd:
     whole: "{output_folder}/*prd*.md"
     sharded: "{output_folder}/*prd*/index.md"
-
   epics:
     whole: "{output_folder}/*epic*.md"
     sharded: "{output_folder}/*epic*/index.md"
-
   ux_design:
     whole: "{output_folder}/*ux*.md"
     sharded: "{output_folder}/*ux*/index.md"
-
   document_project:
-    sharded: "{output_folder}/docs/index.md"
+    sharded: "{output_folder}/index.md"
 
 # Module path and component files
 installed_path: "{project-root}/{bmad_folder}/bmm/workflows/3-solutioning/architecture"
@@ -50,20 +41,6 @@ pattern_categories: "{installed_path}/pattern-categories.csv"
 # Output configuration
 default_output_file: "{output_folder}/architecture.md"
 
-# Workflow metadata
-version: "1.3.2"
-replaces: "architecture"
-paradigm: "facilitation-driven"
-execution_time: "30-90 minutes depending on user skill level"
-features:
-  - "Starter template discovery and integration"
-  - "Dynamic version verification via web search"
-  - "Adaptive facilitation by skill level"
-  - "Decision-focused architecture"
-  - "Novel pattern design for unique concepts"
-  - "Intelligent pattern identification - LLM figures out what patterns matter"
-  - "Implementation patterns for agent consistency"
-
 standalone: true
 
 # Web bundle configuration for standalone deployment