architecture name standardization

src/modules/bmm/workflows/2-plan-workflows/README.md

@@ -27,25 +27,25 @@ The workflow routes to different planning approaches based on project level:
 **Planning:** PRD (product-focused) + Tech-spec (technical planning)
 **Output:** `PRD.md`, `epics.md`, `tech-spec.md`
 **Next Phase:** Tech-spec workflow (lightweight solutioning), then implementation (Phase 4)
-**Note:** Level 2 uses tech-spec instead of full solution-architecture to keep planning lightweight
+**Note:** Level 2 uses tech-spec instead of full architecture to keep planning lightweight
 
 ### Level 3 - Medium Project (15-40 stories, 2-5 epics)
 
 **Planning:** PRD (strategic product document)
 **Output:** `PRD.md`, `epics.md`
-**Next Phase:** Solution-architecture workflow (Phase 3), then implementation (Phase 4)
+**Next Phase:** create-architecture workflow (Phase 3), then implementation (Phase 4)
 
 ### Level 4 - Large/Enterprise Project (40-100+ stories, 5-10 epics)
 
 **Planning:** PRD (comprehensive product specification)
 **Output:** `PRD.md`, `epics.md`
-**Next Phase:** Solution-architecture workflow (Phase 3), then implementation (Phase 4)
+**Next Phase:** create-architecture workflow (Phase 3), then implementation (Phase 4)
 
 **Critical Distinction:**
 
 - **Levels 0-1:** No PRD, tech-spec only
 - **Level 2:** PRD + tech-spec (skips full architecture)
-- **Levels 3-4:** PRD → full solution-architecture workflow
+- **Levels 3-4:** PRD → full create-architecture workflow
 
 Critical to v6's flow improvement is this workflow's integration with the bmm-workflow-status.md tracking document, which maintains project state across sessions, tracks which agents participate in each phase, and provides continuity for multi-session planning efforts. The workflow can resume from any point, intelligently detecting existing artifacts and determining next steps without redundant work. For UX-heavy projects, it can generate standalone UX specifications or AI frontend prompts from existing specs.
 
@@ -138,7 +138,7 @@ The workflow adapts automatically based on project assessment, but key configura
 
 - PRD workflow (comprehensive product specification)
 - Generates `PRD.md` and `epics.md`
-- Hands off to Phase 3 (solution-architecture workflow)
+- Hands off to Phase 3 (create-architecture workflow)
 - Full architecture design before implementation
 
 ### Phase 3: Validation and Handoff (Final steps)
@@ -177,7 +177,7 @@ The workflow adapts automatically based on project assessment, but key configura
 
 - `PRD.md` - Comprehensive product specification
 - `epics.md` - Complete epic/story breakdown
-- Hands off to solution-architecture workflow (Phase 3)
+- Hands off to create-architecture workflow (Phase 3)
 - `architecture.md` - Generated by architect workflow
 - Then to implementation
 

src/modules/bmm/workflows/2-plan-workflows/gdd/instructions-gdd.md

@@ -390,10 +390,10 @@ Since this is a Level {{project_level}} game project, you need solutioning for p
 
 <action>Generate comprehensive checklist based on project analysis</action>
 
-### Phase 1: Solution Architecture and Engine Selection
+### Phase 1: Architecture and Engine Selection
 
 - [ ] **Run solutioning workflow** (REQUIRED)
-  - Command: `workflow solution-architecture`
+  - Command: `workflow create-architecture`
   - Input: GDD.md, bmm-workflow-status.md
   - Output: architecture.md with engine/platform specifics
   - Note: Registry.csv will provide engine-specific guidance

src/modules/bmm/workflows/2-plan-workflows/prd/checklist.md

@@ -84,7 +84,7 @@
 
 ### If Level 3-4:
 
-- [ ] PRD provides sufficient context for solution-architecture workflow
+- [ ] PRD provides sufficient context for create-architecture workflow
 - [ ] Epic structure supports phased delivery approach
 - [ ] Clear value delivery path through epic sequence
 

src/modules/bmm/workflows/2-plan-workflows/prd/instructions.md

@@ -438,7 +438,7 @@ For each epic from the epic list, expand with full story details:
 {{#if project_level >= 3}}
 
 - Review PRD and epics with stakeholders
-- **Next:** Run `solution-architecture` for full technical design
+- **Next:** Run `create-architecture` for full technical design
 - Then proceed to implementation
   {{/if}}
 

src/modules/bmm/workflows/2-plan-workflows/prd/workflow.yaml

@@ -1,6 +1,6 @@
 # Product Requirements Document (PRD) Workflow
 name: prd
-description: "Unified PRD workflow for project levels 2-4. Produces strategic PRD and tactical epic breakdown. Hands off to solution-architecture workflow for technical design. Note: Level 0-1 use tech-spec workflow."
+description: "Unified PRD workflow for project levels 2-4. Produces strategic PRD and tactical epic breakdown. Hands off to architecture workflow for technical design. Note: Level 0-1 use tech-spec workflow."
 author: "BMad"
 
 # Critical variables from config
@@ -35,7 +35,7 @@ recommended_inputs:
 
 web_bundle:
   name: "prd"
-  description: "Unified PRD workflow for project levels 2-4. Produces strategic PRD and tactical epic breakdown. Hands off to solution-architecture workflow for technical design. Note: Level 0-1 use tech-spec workflow."
+  description: "Unified PRD workflow for project levels 2-4. Produces strategic PRD and tactical epic breakdown. Hands off to architecture workflow for technical design. Note: Level 0-1 use tech-spec workflow."
   author: "BMad"
   instructions: "bmad/bmm/workflows/2-plan-workflows/prd/instructions.md"
   web_bundle_files: