1-analysis workflow-state yaml streamlined

bmad/bmb/workflows/convert-legacy/instructions.md

@@ -258,10 +258,10 @@ For Modules:
    - Preserve execution logic
 
 4. Handle special v4 patterns:
-   - 1-9 elicitation menus → v5 <invoke-task halt="true">{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>
+   - 1-9 elicitation menus → <invoke-task halt="true">{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>
    - Agent permissions → note in instructions
-   - YOLO mode → autonomous flag or optional steps
-   - Critical notices → workflow.yaml comments
+   - YOLO mode → agent will decide how to handle yolo at runtime
+   - Critical notices → workflow.yaml comments or strict action or other tag in instructions as needed
 
 <invoke-workflow>
   workflow: {project-root}/bmad/bmb/workflows/create-workflow/workflow.yaml

src/modules/bmm/workflows/1-analysis/workflow-status/workflow.yaml

@@ -17,20 +17,4 @@ instructions: "{installed_path}/instructions.md"
 # Output configuration - no output file, reads existing status
 default_output_file: ""
 
-required_tools:
-  - list_files
-  - read_file
-  - glob
-
-tags:
-  - workflow-orchestration
-  - status-tracking
-  - master-router
-  - bmad-v6
-
-execution_hints:
-  interactive: true # User interaction required for decisions
-  autonomous: false # Requires user input
-  iterative: false # Single-pass status check and suggestion
-
 web_bundle: false

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

@@ -4,6 +4,7 @@
 
 <critical>The workflow execution engine is governed by: {project_root}/bmad/core/tasks/workflow.xml</critical>
 <critical>You MUST have already loaded and processed: {installed_path}/workflow.yaml</critical>
+<critical>Communicate all responses in {communication_language}</critical>
 <critical>This is the GDD instruction set for GAME projects - replaces PRD with Game Design Document</critical>
 <critical>Project analysis already completed - proceeding with game-specific design</critical>
 <critical>Uses gdd_template for GDD output, game_types.csv for type-specific sections</critical>
@@ -528,7 +529,9 @@ Since this is a Level {{project_level}} game project, you need solutioning for p
   - Milestone planning
   - Demo/playable builds
 
-<ask>GDD Complete! Next immediate action:
+<ask>**✅ GDD Complete, {user_name}!**
+
+Next immediate action:
 
 </check>
 

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

@@ -28,29 +28,6 @@ recommended_inputs:
   - narrative_design: "{output_folder}/narrative-design.md"
   - market_research: "{output_folder}/market-research.md"
 
-# Claude Code integration points
-claude_code_enhancements:
-  - injection_point: "game-design-subagents"
-  - available_subagents:
-      - game-designer: "Core game mechanics and systems design"
-      - game-architect: "Technical architecture for game systems"
-      - user-researcher: "Player experience and engagement"
-
-# Workflow configuration
-interactive: true # User checkpoints throughout
-autonomous: false # Requires user input
-allow_parallel: false # Sequential design process
-
-# Game frameworks available
-frameworks:
-  - "MDA Framework (Mechanics, Dynamics, Aesthetics)"
-  - "Core Loop Design"
-  - "Progression Systems"
-  - "Economy Design"
-  - "Difficulty Curves"
-  - "Player Psychology"
-  - "Game Feel and Juice"
-
 web_bundle:
   name: "gdd"
   description: "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."
@@ -84,16 +61,3 @@ web_bundle:
     - "bmad/bmm/workflows/2-plan-workflows/gdd/game-types/tower-defense.md"
     - "bmad/bmm/workflows/2-plan-workflows/gdd/game-types/turn-based-tactics.md"
     - "bmad/bmm/workflows/2-plan-workflows/gdd/game-types/visual-novel.md"
-  # Game frameworks available
-  frameworks:
-    - "MDA Framework (Mechanics, Dynamics, Aesthetics)"
-    - "Core Loop Design"
-    - "Progression Systems"
-    - "Economy Design"
-    - "Difficulty Curves"
-    - "Player Psychology"
-    - "Game Feel and Juice"
-  # Workflow configuration
-  interactive: true # User checkpoints throughout
-  autonomous: false # Requires user input
-  allow_parallel: false # Sequential design process

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

@@ -4,6 +4,7 @@
 
 <critical>The workflow execution engine is governed by: {project_root}/bmad/core/tasks/workflow.xml</critical>
 <critical>You MUST have already completed the GDD workflow</critical>
+<critical>Communicate all responses in {communication_language}</critical>
 <critical>This workflow creates detailed narrative content for story-driven games</critical>
 <critical>Uses narrative_template for output</critical>
 <critical>If users mention gameplay mechanics, note them but keep focus on narrative</critical>
@@ -508,7 +509,9 @@ Your references:</ask>
 
 <template-output>references</template-output>
 
-<ask>Narrative Design complete! Next steps:
+<ask>**✅ Narrative Design Complete, {user_name}!**
+
+Next steps:
 
 1. Proceed to solutioning (technical architecture)
 2. Create detailed script/screenplay (outside workflow)

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

@@ -24,21 +24,6 @@ recommended_inputs:
   - gdd: "{output_folder}/GDD.md"
   - product_brief: "{output_folder}/product-brief.md"
 
-# Workflow configuration
-interactive: true # User checkpoints throughout
-autonomous: false # Requires user input
-allow_parallel: false # Sequential narrative development
-
-# Narrative frameworks available
-frameworks:
-  - "Hero's Journey"
-  - "Three-Act Structure"
-  - "Character Arc Development"
-  - "Branching Narrative Design"
-  - "Environmental Storytelling"
-  - "Dialogue Systems"
-  - "Narrative Pacing"
-
 web_bundle:
   name: "narrative"
   description: "Narrative design workflow for story-driven games and applications. Creates comprehensive narrative documentation including story structure, character arcs, dialogue systems, and narrative implementation guidance."
@@ -47,17 +32,3 @@ web_bundle:
   web_bundle_files:
     - "bmad/bmm/workflows/2-plan-workflows/narrative/instructions-narrative.md"
     - "bmad/bmm/workflows/2-plan-workflows/narrative/narrative-template.md"
-  recommended_inputs: "PRD, Product Brief, Brain Storming Report, GDD"
-  # Narrative frameworks available
-  frameworks:
-    - "Hero's Journey"
-    - "Three-Act Structure"
-    - "Character Arc Development"
-    - "Branching Narrative Design"
-    - "Environmental Storytelling"
-    - "Dialogue Systems"
-    - "Narrative Pacing"
-  # Workflow configuration
-  interactive: true # User checkpoints throughout
-  autonomous: false # Requires user input
-  allow_parallel: false # Sequential narrative development

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

@@ -2,6 +2,7 @@
 
 <critical>The workflow execution engine is governed by: {project-root}/bmad/core/tasks/workflow.xml</critical>
 <critical>You MUST have already loaded and processed: {installed_path}/workflow.yaml</critical>
+<critical>Communicate all responses in {communication_language}</critical>
 <critical>This workflow is for Level 2-4 projects. Level 0-1 use tech-spec workflow.</critical>
 <critical>Produces TWO outputs: PRD.md (strategic) and epics.md (tactical implementation)</critical>
 <critical>TECHNICAL NOTES: If ANY technical details, preferences, or constraints are mentioned during PRD discussions, append them to {technical_decisions_file}. If file doesn't exist, create it from {technical_decisions_template}</critical>
@@ -397,7 +398,7 @@ For each epic from the epic list, expand with full story details:
 
 <template-output file="bmm-workflow-status.md">prd_completion_update</template-output>
 
-**Workflow Complete!**
+**✅ PRD Workflow Complete, {user_name}!**
 
 **Deliverables Created:**
 

src/modules/bmm/workflows/2-plan-workflows/tech-spec/instructions.md

@@ -4,6 +4,7 @@
 
 <critical>The workflow execution engine is governed by: {project_root}/bmad/core/tasks/workflow.xml</critical>
 <critical>You MUST have already loaded and processed: {installed_path}/workflow.yaml</critical>
+<critical>Communicate all responses in {communication_language}</critical>
 <critical>This is the SMALL instruction set for Level 0-1 projects - tech-spec with story generation</critical>
 <critical>Level 0: tech-spec + single user story | Level 1: tech-spec + epic/stories</critical>
 <critical>Project analysis already completed - proceeding directly to technical specification</critical>
@@ -233,7 +234,9 @@ Run cohesion validation? (y/n)</ask>
   - Command: `workflow task-generation`
   - Uses: tech-spec.md
 
-<ask>Level 0 planning complete! Next action:
+<ask>**✅ Tech-Spec Complete, {user_name}!**
+
+Next action:
 
 1. Proceed to implementation
 2. Generate development task

src/modules/bmm/workflows/2-plan-workflows/tech-spec/workflow.yaml

@@ -34,26 +34,6 @@ recommended_inputs:
   - bug_report: "Bug description or issue ticket"
   - feature_request: "Brief feature description"
 
-# Claude Code integration points
-claude_code_enhancements:
-  - injection_point: "tech-spec-subagents"
-  - available_subagents:
-      - technical-evaluator: "Technology assessment and feasibility"
-      - codebase-analyzer: "Existing code analysis"
-      - pattern-detector: "Identify coding patterns to follow"
-
-# Workflow configuration
-interactive: true # User checkpoints
-autonomous: false # Requires user input
-allow_parallel: false # Sequential specification
-
-# Technical frameworks available
-frameworks:
-  - "Technical Design Patterns"
-  - "API Design Principles"
-  - "Code Organization Standards"
-  - "Testing Strategies"
-
 web_bundle:
   name: "tech-spec-sm"
   description: "Technical specification workflow for Level 0-1 projects. Creates focused tech spec with story generation. Level 0: tech-spec + user story. Level 1: tech-spec + epic/stories."
@@ -66,13 +46,3 @@ web_bundle:
     - "bmad/bmm/workflows/2-plan-workflows/tech-spec/tech-spec-template.md"
     - "bmad/bmm/workflows/2-plan-workflows/tech-spec/user-story-template.md"
     - "bmad/bmm/workflows/2-plan-workflows/tech-spec/epics-template.md"
-  # Technical frameworks available
-  frameworks:
-    - "Technical Design Patterns"
-    - "API Design Principles"
-    - "Code Organization Standards"
-    - "Testing Strategies"
-  # Workflow configuration
-  interactive: true # User checkpoints
-  autonomous: false # Requires user input
-  allow_parallel: false # Sequential specification

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

@@ -4,6 +4,7 @@
 
 <critical>The workflow execution engine is governed by: {project_root}/bmad/core/tasks/workflow.xml</critical>
 <critical>You MUST have already loaded and processed: {installed_path}/workflow.yaml</critical>
+<critical>Communicate all responses in {communication_language}</critical>
 <critical>This workflow creates comprehensive UX/UI specifications - can run standalone or as part of plan-project</critical>
 <critical>Uses ux-spec-template.md for structured output generation</critical>
 <critical>Can optionally generate AI Frontend Prompts for tools like Vercel v0, Lovable.ai</critical>
@@ -301,7 +302,9 @@ This is recommended for:
 
 <template-output>design_handoff_checklist</template-output>
 
-<ask>UX Specification saved to {{ux_spec_file}}
+<ask>**✅ UX Specification Complete, {user_name}!**
+
+UX Specification saved to {{ux_spec_file}}
 
 **Additional Output Options:**
 

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

@@ -25,28 +25,6 @@ recommended_inputs:
   - product_brief: "{output_folder}/product-brief.md"
   - gdd: "{output_folder}/GDD.md"
 
-# Claude Code integration points
-claude_code_enhancements:
-  - injection_point: "ux-subagents"
-  - available_subagents:
-      - ux-expert: "User experience design and best practices"
-      - user-researcher: "User research and persona development"
-
-# Workflow configuration
-interactive: true # User checkpoints throughout
-autonomous: false # Requires user input
-allow_parallel: false # Sequential UX design process
-
-# UX frameworks available
-frameworks:
-  - "User-Centered Design"
-  - "Design System Principles"
-  - "Accessibility (WCAG)"
-  - "Responsive Design"
-  - "Component-Based Design"
-  - "Atomic Design"
-  - "Material Design / Human Interface Guidelines"
-
 web_bundle:
   name: "ux-spec"
   description: "UX/UI specification workflow for defining user experience and interface design. Creates comprehensive UX documentation including wireframes, user flows, component specifications, and design system guidelines."
@@ -55,17 +33,3 @@ web_bundle:
   web_bundle_files:
     - "bmad/bmm/workflows/2-plan-workflows/ux/instructions-ux.md"
     - "bmad/bmm/workflows/2-plan-workflows/ux/ux-spec-template.md"
-  recommended_inputs: "PRD, Product Brief, Brain Storming Report, GDD"
-  # UX frameworks available
-  frameworks:
-    - "User-Centered Design"
-    - "Design System Principles"
-    - "Accessibility (WCAG)"
-    - "Responsive Design"
-    - "Component-Based Design"
-    - "Atomic Design"
-    - "Material Design / Human Interface Guidelines"
-  # Workflow configuration
-  interactive: true # User checkpoints throughout
-  autonomous: false # Requires user input
-  allow_parallel: false # Sequential UX design process

workflow-cleanup-progress.md

@@ -213,6 +213,58 @@ date: system-generated
 
 **This serves as the reference implementation for converting prescriptive workflows to intent-based style.**
 
+### 2025-10-16: Completed ALL 2-plan-workflows (5/5 - 100%)
+
+**✅ Phase 2-Plan-Workflows Module Complete!**
+
+All 5 workflows in the 2-plan-workflows folder have been audited, cleaned, and optimized:
+
+1. ✅ **gdd** - YAML CLEANUP + CRITICAL HEADERS
+   - Removed claude_code_enhancements bloat
+   - Removed duplicate frameworks section
+   - Removed duplicate workflow configuration (interactive/autonomous/allow_parallel)
+   - Added {communication_language} critical header
+   - Added {user_name} personalization in completion message
+
+2. ✅ **narrative** - YAML CLEANUP + CRITICAL HEADERS
+   - Removed duplicate frameworks section
+   - Removed duplicate workflow configuration
+   - Added {communication_language} critical header
+   - Added {user_name} personalization in completion message
+
+3. ✅ **prd** - CLEAN YAML + CRITICAL HEADERS
+   - YAML was already clean (no bloat)
+   - Added {communication_language} critical header
+   - Added {user_name} personalization in completion message
+
+4. ✅ **tech-spec** - YAML CLEANUP + CRITICAL HEADERS
+   - Removed claude_code_enhancements bloat
+   - Removed duplicate frameworks section
+   - Removed duplicate workflow configuration
+   - Added {communication_language} critical header
+   - Added {user_name} personalization in completion message
+
+5. ✅ **ux** - YAML CLEANUP + CRITICAL HEADERS
+   - Removed claude_code_enhancements bloat
+   - Removed duplicate frameworks section
+   - Removed duplicate workflow configuration
+   - Added {communication_language} critical header
+   - Added {user_name} personalization in completion message
+
+**Common Bloat Pattern Removed:**
+
+- `claude_code_enhancements` sections (4 workflows)
+- Duplicate `frameworks` lists in top-level and web_bundle (4 workflows)
+- Duplicate `interactive/autonomous/allow_parallel` config (4 workflows)
+
+**Standard Additions Applied:**
+
+- {communication_language} critical header in all instruction files
+- {user_name} personalization in all completion messages
+- All workflows now follow standard config usage pattern
+
+---
+
 ### 2025-10-16: Completed ALL 1-analysis Workflows (7/7 - 100%)
 
 **✅ Phase 1-Analysis Module Complete!**
@@ -282,6 +334,13 @@ All 7 workflows in the 1-analysis folder have been audited, cleaned, and optimiz
 
 **Phase 1:** ✅ 3/3 files updated (100%)
 **Phase 2:** ✅ 34/34 workflows updated (100%)
-**Phase 3:** ⏳ 0/34 workflows cleaned (0%)
+**Phase 3:** ⚙️ 16/35 workflows cleaned (46%)
 
-**Overall Progress:** 67% complete (2/3 phases done)
+- CIS: 4/4 (100%)
+- BMM 1-analysis: 7/7 (100%)
+- BMM 2-plan-workflows: 5/5 (100%)
+- BMM 3-solutioning: 0/8 (0%)
+- BMM 4-implementation: 0/5 (0%)
+- BMB: 0/8 (0%)
+
+**Overall Progress:** 80% complete (Phase 1 + Phase 2 + 46% of Phase 3)