more step sharded workflows added for architecture and some fixes across all workflows to improve their file loading and reduction of time based estimates.

src/modules/bmm/workflows/1-analysis/product-brief/steps/step-01-init.md

@@ -3,6 +3,9 @@
 ## MANDATORY EXECUTION RULES (READ FIRST):
 
 - 🛑 NEVER generate content without user input
+
+- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions
+- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding
 - ✅ ALWAYS treat this as collaborative discovery between PM peers
 - 📋 YOU ARE A FACILITATOR, not a content generator
 - 💬 FOCUS on initialization and setup only - don't look ahead to future steps
@@ -32,7 +35,7 @@ Initialize the product brief workflow by detecting continuation state and settin
 
 First, check if the output document already exists:
 
-- Look for file at `{output_folder}/product-brief-{{project_name}}-{{date}}.md`
+- Look for file at `{output_folder}/analysis/*product-brief*.md`
 - If exists, read the complete file including frontmatter
 - If not exists, this is a fresh workflow
 
@@ -54,16 +57,16 @@ Discover and load context documents using smart discovery:
 
 **Research Documents (Priority: Sharded → Whole):**
 
-1. Check for sharded research folder: `{output_folder}/*research*/**/*.md`
+1. Check for sharded research folder: `{output_folder}/analysis/research/**/*.md`
 2. If folder exists: Load EVERY file in that folder completely for comprehensive research context
-3. If no folder exists: Try whole file: `{output_folder}/*research*.md`
+3. If no folder exists: Try whole file: `{output_folder}/analysis/research/*research*.md`
 4. Add discovered files to `inputDocuments` frontmatter
 
 **Brainstorming Documents (Priority: Sharded → Whole):**
 
-1. Check for sharded brainstorming folder: `{output_folder}/*brainstorm*/**/*.md`
+1. Check for sharded brainstorming folder: `{output_folder}/analysis/*brainstorm*/**/*.md`
 2. If folder exists: Load useful brainstorming files completely
-3. If no folder exists: Try whole file: `{output_folder}/*brainstorm*.md`
+3. If no folder exists: Try whole file: `{output_folder}/analysis/*brainstorm*.md`
 4. Add discovered files to `inputDocuments` frontmatter
 
 **Project Documentation (Existing Projects):**
@@ -137,6 +140,10 @@ Do you have any other documents you'd like me to include, or shall we continue t
 ❌ Not checking sharded folders first before whole files
 ❌ Not reporting what documents were found to user
 
+❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions
+❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file
+❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols
+
 ## NEXT STEP:
 
 After user selects [C] to continue, load `./step-02-vision.md` to begin the product vision discovery phase.

src/modules/bmm/workflows/1-analysis/product-brief/steps/step-01b-continue.md

@@ -3,6 +3,9 @@
 ## MANDATORY EXECUTION RULES (READ FIRST):
 
 - 🛑 NEVER generate content without user input
+
+- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions
+- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding
 - ✅ ALWAYS treat this as collaborative discovery between PM peers
 - 📋 YOU ARE A FACILITATOR, not a content generator
 - 💬 FOCUS on understanding where we left off and continuing appropriately
@@ -94,6 +97,10 @@ After presenting current progress, ask:
 ❌ Loading wrong next step based on `lastStep` value
 ❌ Proceeding without user confirmation of current state
 
+❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions
+❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file
+❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols
+
 ## WORKFLOW ALREADY COMPLETE?
 
 If `lastStep = 6` (final step completed):

src/modules/bmm/workflows/1-analysis/product-brief/steps/step-02-vision.md

@@ -3,6 +3,9 @@
 ## MANDATORY EXECUTION RULES (READ FIRST):
 
 - 🛑 NEVER generate content without user input
+
+- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions
+- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding
 - ✅ ALWAYS treat this as collaborative discovery between PM peers
 - 📋 YOU ARE A FACILITATOR, not a content generator
 - 💬 FOCUS on product vision, problem, and solution discovery only
@@ -27,7 +30,7 @@ This step will generate content and present choices:
 ## PROTOCOL INTEGRATION:
 
 - When 'A' selected: Execute {project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml
-- When 'P' selected: Execute {project-root}/{bmad_folder}/core/workflows/party-mode
+- When 'P' selected: Execute {project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md
 - PROTOCOLS always return to this step's A/P/C menu
 - User accepts/rejects protocol changes before proceeding
 
@@ -159,7 +162,7 @@ Show the generated content and present choices:
 
 #### If 'A' (Advanced Elicitation):
 
-- Execute advanced-elicitation.xml with the current vision content
+- Execute {project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml with the current vision content
 - Process the enhanced vision insights that come back
 - Ask user: "Accept these improvements to the product vision? (y/n)"
 - If yes: Update content with improvements, then return to A/P/C menu
@@ -167,7 +170,7 @@ Show the generated content and present choices:
 
 #### If 'P' (Party Mode):
 
-- Execute party-mode workflow with the current vision content
+- Execute {project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md with the current vision content
 - Process the collaborative vision exploration and positioning insights
 - Ask user: "Accept these changes to the product vision? (y/n)"
 - If yes: Update content with improvements, then return to A/P/C menu
@@ -201,6 +204,10 @@ When user selects 'C', append the content directly to the document using the str
 ❌ Not presenting A/P/C menu after content generation
 ❌ Appending content without user selecting 'C'
 
+❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions
+❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file
+❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols
+
 ## CONTEXT INPUTS:
 
 If research or brainstorming documents were loaded in step 1, incorporate insights from those documents into the vision discovery:

src/modules/bmm/workflows/1-analysis/product-brief/steps/step-03-users.md

@@ -3,6 +3,9 @@
 ## MANDATORY EXECUTION RULES (READ FIRST):
 
 - 🛑 NEVER generate content without user input
+
+- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions
+- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding
 - ✅ ALWAYS treat this as collaborative discovery between PM peers
 - 📋 YOU ARE A FACILITATOR, not a content generator
 - 💬 FOCUS on defining who this product serves and how they interact with it
@@ -27,7 +30,7 @@ This step will generate content and present choices:
 ## PROTOCOL INTEGRATION:
 
 - When 'A' selected: Execute {project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml
-- When 'P' selected: Execute {project-root}/{bmad_folder}/core/workflows/party-mode
+- When 'P' selected: Execute {project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md
 - PROTOCOLS always return to this step's A/P/C menu
 - User accepts/rejects protocol changes before proceeding
 
@@ -158,7 +161,7 @@ Show the generated user content and present choices:
 
 #### If 'A' (Advanced Elicitation):
 
-- Execute advanced-elicitation.xml with the current user content
+- Execute {project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml with the current user content
 - Process the enhanced user insights that come back
 - Ask user: "Accept these improvements to the target users? (y/n)"
 - If yes: Update content with improvements, then return to A/P/C menu
@@ -166,7 +169,7 @@ Show the generated user content and present choices:
 
 #### If 'P' (Party Mode):
 
-- Execute party-mode workflow with the current user personas
+- Execute {project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md with the current user personas
 - Process the collaborative user validation and additional insights
 - Ask user: "Accept these changes to the target users? (y/n)"
 - If yes: Update content with improvements, then return to A/P/C menu
@@ -200,6 +203,10 @@ When user selects 'C', append the content directly to the document using the str
 ❌ Not presenting A/P/C menu after content generation
 ❌ Appending content without user selecting 'C'
 
+❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions
+❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file
+❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols
+
 ## USER INSIGHTS SOURCES:
 
 If user research documents were loaded in step 1, incorporate those insights:

src/modules/bmm/workflows/1-analysis/product-brief/steps/step-04-metrics.md

@@ -3,6 +3,9 @@
 ## MANDATORY EXECUTION RULES (READ FIRST):
 
 - 🛑 NEVER generate content without user input
+
+- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions
+- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding
 - ✅ ALWAYS treat this as collaborative discovery between PM peers
 - 📋 YOU ARE A FACILITATOR, not a content generator
 - 💬 FOCUS on defining measurable success criteria and business objectives
@@ -27,7 +30,7 @@ This step will generate content and present choices:
 ## PROTOCOL INTEGRATION:
 
 - When 'A' selected: Execute {project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml
-- When 'P' selected: Execute {project-root}/{bmad_folder}/core/workflows/party-mode
+- When 'P' selected: Execute {project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md
 - PROTOCOLS always return to this step's A/P/C menu
 - User accepts/rejects protocol changes before proceeding
 
@@ -161,7 +164,7 @@ Show the generated metrics content and present choices:
 
 #### If 'A' (Advanced Elicitation):
 
-- Execute advanced-elicitation.xml with the current metrics content
+- Execute {project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml with the current metrics content
 - Process the enhanced metric insights that come back
 - Ask user: "Accept these improvements to the success metrics? (y/n)"
 - If yes: Update content with improvements, then return to A/P/C menu
@@ -169,7 +172,7 @@ Show the generated metrics content and present choices:
 
 #### If 'P' (Party Mode):
 
-- Execute party-mode workflow with the current success metrics
+- Execute {project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md with the current success metrics
 - Process the collaborative metric validation and additional insights
 - Ask user: "Accept these changes to the success metrics? (y/n)"
 - If yes: Update content with improvements, then return to A/P/C menu
@@ -203,6 +206,10 @@ When user selects 'C', append the content directly to the document using the str
 ❌ Not presenting A/P/C menu after content generation
 ❌ Appending content without user selecting 'C'
 
+❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions
+❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file
+❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols
+
 ## METRIC QUALITY CRITERIA:
 
 **Good Metrics:**

src/modules/bmm/workflows/1-analysis/product-brief/steps/step-05-scope.md

@@ -3,6 +3,9 @@
 ## MANDATORY EXECUTION RULES (READ FIRST):
 
 - 🛑 NEVER generate content without user input
+
+- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions
+- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding
 - ✅ ALWAYS treat this as collaborative discovery between PM peers
 - 📋 YOU ARE A FACILITATOR, not a content generator
 - 💬 FOCUS on defining minimum viable scope and future vision
@@ -27,7 +30,7 @@ This step will generate content and present choices:
 ## PROTOCOL INTEGRATION:
 
 - When 'A' selected: Execute {project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml
-- When 'P' selected: Execute {project-root}/{bmad_folder}/core/workflows/party-mode
+- When 'P' selected: Execute {project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md
 - PROTOCOLS always return to this step's A/P/C menu
 - User accepts/rejects protocol changes before proceeding
 
@@ -175,7 +178,7 @@ Show the generated scope content and present choices:
 
 #### If 'A' (Advanced Elicitation):
 
-- Execute advanced-elicitation.xml with the current scope content
+- Execute {project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml with the current scope content
 - Process the enhanced scope insights that come back
 - Ask user: "Accept these improvements to the MVP scope? (y/n)"
 - If yes: Update content with improvements, then return to A/P/C menu
@@ -183,7 +186,7 @@ Show the generated scope content and present choices:
 
 #### If 'P' (Party Mode):
 
-- Execute party-mode workflow with the current MVP scope
+- Execute {project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md with the current MVP scope
 - Process the collaborative scope validation and prioritization
 - Ask user: "Accept these changes to the MVP scope? (y/n)"
 - If yes: Update content with improvements, then return to A/P/C menu
@@ -217,6 +220,10 @@ When user selects 'C', append the content directly to the document using the str
 ❌ Not presenting A/P/C menu after content generation
 ❌ Appending content without user selecting 'C'
 
+❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions
+❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file
+❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols
+
 ## SCOPE NEGOTIATION PRINCIPLES:
 
 **MVP Mindset:**

src/modules/bmm/workflows/1-analysis/product-brief/steps/step-06-complete.md

@@ -3,6 +3,9 @@
 ## MANDATORY EXECUTION RULES (READ FIRST):
 
 - ✅ THIS IS A FINAL STEP - Product brief completion required
+
+- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions
+- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding
 - 🛑 NO content generation - this is a wrap-up step
 - 📋 FINALIZE document and update workflow status
 - 💬 FOCUS on completion, next steps, and suggestions
@@ -146,6 +149,10 @@ The brief captures everything needed to guide subsequent product development:
 ❌ Workflow not properly marked as complete in status tracking
 ❌ User unclear about what happens next
 
+❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions
+❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file
+❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols
+
 ## PRODUCT BRIEF COMPLETION CHECKLIST:
 
 ### Document Structure Complete:

src/modules/bmm/workflows/1-analysis/research/domain-steps/step-01-init.md

@@ -1,39 +1,26 @@
-# Domain Research Step 1: Initialization and Context
+# Domain Research Step 1: Domain Research Scope Confirmation
 
 ## MANDATORY EXECUTION RULES (READ FIRST):
 
-- 🛑 NEVER generate content without user input
-- ✅ ALWAYS treat this as collaborative research partnership
-- 📋 YOU ARE A RESEARCH FACILITATOR, not content generator
-- 💬 FOCUS on domain/industry research with current web data
-- 🔍 WEB RESEARCH REQUIRED - Use {{current_year}} data and verify sources
+- 🛑 NEVER generate content without user confirmation
+
+- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions
+- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding
+- ✅ FOCUS EXCLUSIVELY on confirming domain research scope and approach
+- 📋 YOU ARE A DOMAIN RESEARCH PLANNER, not content generator
+- 💬 ACKNOWLEDGE and CONFIRM understanding of domain research goals
+- 🔍 This is SCOPE CONFIRMATION ONLY - no web research yet
 
 ## EXECUTION PROTOCOLS:
 
 - 🎯 Show your analysis before taking any action
-- ⚠️ Present A/P/C menu after initial context generation
-- 💾 ONLY save when user chooses C (Continue)
+- ⚠️ Present [C] continue option after scope confirmation
+- 💾 ONLY proceed when user chooses C (Continue)
 - 📖 Update frontmatter `stepsCompleted: [1]` before loading next step
 - 🚫 FORBIDDEN to load next step until C is selected
 
-## COLLABORATION MENUS (A/P/C):
-
-This step will generate content and present choices:
-
-- **A (Advanced Elicitation)**: Use discovery protocols to develop deeper domain insights
-- **P (Party Mode)**: Bring multiple perspectives to validate domain scope
-- **C (Continue)**: Save the content to the document and proceed to next step
-
-## PROTOCOL INTEGRATION:
-
-- When 'A' selected: Execute {project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml
-- When 'P' selected: Execute {project-root}/{bmad_folder}/core/workflows/party-mode
-- PROTOCOLS always return to this step's A/P/C menu
-- User accepts/rejects protocol changes before proceeding
-
 ## CONTEXT BOUNDARIES:
 
-- Current document and frontmatter from main workflow are available
 - Research type = "domain" is already set
 - **Research topic = "{{research_topic}}"** - discovered from initial discussion
 - **Research goals = "{{research_goals}}"** - captured from initial discussion
@@ -42,157 +29,108 @@ This step will generate content and present choices:
 
 ## YOUR TASK:
 
-Initialize domain research scope and approach for the already-identified topic: **{{research_topic}}**
+Confirm domain research scope and approach for **{{research_topic}}** with the user's goals in mind.
 
-## DOMAIN RESEARCH INITIALIZATION:
+## DOMAIN SCOPE CONFIRMATION:
 
-### 1. Confirm Domain Research Direction
+### 1. Begin Scope Confirmation
 
-Begin with domain-specific positioning:
-"I'll guide you through **domain research** for **{{research_topic}}** using current {{current_year}} web data with rigorous source verification.
+Start with domain scope understanding:
+"I understand you want to conduct **domain research** for **{{research_topic}}** with these goals: {{research_goals}}
 
-**Research Goals Identified:** {{research_goals}}
+**Domain Research Scope:**
 
-**Domain Research Focus for {{research_topic}}:**
+- **Industry Analysis**: Industry structure, market dynamics, and competitive landscape
+- **Regulatory Environment**: Compliance requirements, regulations, and standards
+- **Technology Patterns**: Innovation trends, technology adoption, and digital transformation
+- **Economic Factors**: Market size, growth trends, and economic impact
+- **Supply Chain**: Value chain analysis and ecosystem relationships
 
-- Industry analysis and market dynamics for this domain
-- Regulatory requirements and compliance standards affecting {{research_topic}}
-- Technology trends and innovation patterns in {{research_topic}}
-- Competitive landscape within the {{research_topic}} domain
-- Supply chain and ecosystem analysis
+**Research Approach:**
 
-Let me refine the research scope specifically for **{{research_topic}}**:
+- Current {{current_year}} web data with rigorous source verification
+- Multi-source validation for critical domain claims
+- Confidence levels for uncertain domain information
+- Comprehensive domain coverage with industry-specific insights
 
-### 2. Establish Research Context
+### 2. Scope Confirmation
 
-Refine domain-specific details based on the already-identified topic:
+Present clear scope confirmation:
+"**Domain Research Scope Confirmation:**
 
-#### Context Refinement Questions:
+For **{{research_topic}}**, I will research:
 
-- "What specific aspects of {{research_topic}} are most critical for your goals?"
-- "Are there particular segments or sub-domains within {{research_topic}} we should examine?"
-- "What regulatory or compliance factors most impact {{research_topic}}?"
-- "What time horizon for {{research_topic}} research - current state or include future trends?"
-- "How deep should we analyze the {{research_topic}} domain - overview or comprehensive?"
+✅ **Industry Analysis** - market structure, key players, competitive dynamics
+✅ **Regulatory Requirements** - compliance standards, legal frameworks
+✅ **Technology Trends** - innovation patterns, digital transformation
+✅ **Economic Factors** - market size, growth projections, economic impact
+✅ **Supply Chain Analysis** - value chain, ecosystem, partnerships
 
-### 3. Define Research Scope
+**All using current {{current_year}} web data with source verification.**
 
-Collaboratively establish research boundaries:
+**Does this domain research scope and approach align with your goals?**
+[C] Continue - Begin domain research with this scope
 
-#### Scope Definition:
-
-- "How broad should our domain analysis be?"
-- "Are we looking at global markets or specific regions?"
-- "Should we focus on current state or include future projections?"
-- "What depth of research do you need (overview vs deep dive)?"
-
-### 4. Generate Research Overview Content
-
-Prepare initial content to append to the document:
-
-#### Content Structure:
-
-When saving to document, append these Level 2 and Level 3 sections:
-
-```markdown
-## Research Overview
-
-### Research Objectives
-
-[Domain research objectives based on conversation]
-
-### Scope and Boundaries
-
-[Research scope definition based on conversation]
-
-### Research Methodology
-
-[Research methodology approach with {{current_year}} web data emphasis]
-
-### Source Verification Standards
-
-[Source verification approach and confidence level framework]
-```
-
-### 5. Present Content and Menu
-
-Show the generated overview and present choices:
-"I've established the foundation for our **domain research** with {{current_year}} web data and rigorous source verification.
-
-**Here's what I'll add to the document:**
-
-[Show the complete markdown content from step 4]
-
-**Research Standards:**
-
-- Always using {{current_year}} web searches
-- Requiring multiple sources for critical claims
-- Citing all factual claims with URLs
-- Presenting conflicting information when sources disagree
-- Using confidence levels for uncertain data
-
-**What would you like to do?**
-[A] Advanced Elicitation - Let's deepen our understanding of the domain scope
-[P] Party Mode - Bring different perspectives on domain research approach
-[C] Continue - Save this to the document and begin domain analysis
-
-### 6. Handle Menu Selection
-
-#### If 'A' (Advanced Elicitation):
-
-- Execute advanced-elicitation.xml with current domain overview
-- Process enhanced domain insights that come back
-- Ask user: "Accept these improvements to the research overview? (y/n)"
-- If yes: Update content with improvements, then return to A/P/C menu
-- If no: Keep original content, then return to A/P/C menu
-
-#### If 'P' (Party Mode):
-
-- Execute party-mode workflow with current domain overview
-- Process collaborative domain expertise and additional insights
-- Ask user: "Accept these changes to the research overview? (y/n)"
-- If yes: Update content with improvements, then return to A/P/C menu
-- If no: Keep original content, then return to A/P/C menu
+### 3. Handle Continue Selection
 
 #### If 'C' (Continue):
 
-- Append the final content to the research document
+- Document scope confirmation in research file
 - Update frontmatter: `stepsCompleted: [1]`
-- Load: `./step-02-domain-analysis.md`
+- Load: `./step-02-industry-analysis.md`
 
 ## APPEND TO DOCUMENT:
 
-When user selects 'C', append the content directly to the research document using the structure from step 4.
+When user selects 'C', append scope confirmation:
+
+```markdown
+## Domain Research Scope Confirmation
+
+**Research Topic:** {{research_topic}}
+**Research Goals:** {{research_goals}}
+
+**Domain Research Scope:**
+
+- Industry Analysis - market structure, competitive landscape
+- Regulatory Environment - compliance requirements, legal frameworks
+- Technology Trends - innovation patterns, digital transformation
+- Economic Factors - market size, growth projections
+- Supply Chain Analysis - value chain, ecosystem relationships
+
+**Research Methodology:**
+
+- Current {{current_year}} web data with rigorous source verification
+- Multi-source validation for critical domain claims
+- Confidence level framework for uncertain information
+- Comprehensive domain coverage with industry-specific insights
+
+**Scope Confirmed:** {{date}}
+```
 
 ## SUCCESS METRICS:
 
-✅ Domain research scope clearly defined and confirmed
-✅ Research methodology established with {{current_year}} emphasis
-✅ Source verification standards communicated and documented
-✅ A/P/C menu presented and handled correctly
-✅ Content properly appended to document when C selected
+✅ Domain research scope clearly confirmed with user
+✅ All domain analysis areas identified and explained
+✅ Research methodology with {{current_year}} data emphasized
+✅ [C] continue option presented and handled correctly
+✅ Scope confirmation documented when user proceeds
 ✅ Proper routing to next domain research step
 
 ## FAILURE MODES:
 
-❌ Not confirming specific domain/industry to research
-❌ Missing research scope boundaries
+❌ Not clearly confirming domain research scope with user
+❌ Missing critical domain analysis areas
 ❌ Not emphasizing {{current_year}} web data requirement
-❌ Not communicating source verification protocols
-❌ Not presenting A/P/C menu after content generation
-❌ Appending content without user selecting 'C'
+❌ Not presenting [C] continue option
+❌ Proceeding without user scope confirmation
+❌ Not routing to next domain research step
 
-## WEB RESEARCH READINESS:
-
-This step prepares for web research by:
-
-- Establishing {{current_year}} search query framework
-- Defining source verification protocols
-- Setting confidence level methodology
-- Preparing for multiple source verification of critical claims
+❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions
+❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file
+❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols
 
 ## NEXT STEP:
 
-After user selects 'C' and content is saved to document, load `./step-02-domain-analysis.md` to begin web-based domain analysis with current {{current_year}} data.
+After user selects 'C', load `./step-02-industry-analysis.md` to begin industry analysis with current {{current_year}} web data.
 
-Remember: Always emphasize current {{current_year}} data and rigorous source verification in domain research!
+Remember: This is SCOPE CONFIRMATION ONLY - no actual domain research yet, just confirming the research approach and scope!

src/modules/bmm/workflows/1-analysis/research/domain-steps/step-02-domain-analysis.md

@@ -3,189 +3,226 @@
 ## MANDATORY EXECUTION RULES (READ FIRST):
 
 - 🛑 NEVER generate content without web search verification
-- ✅ ALWAYS use {{current_year}} web searches for current data
-- 📋 YOU ARE A RESEARCH ANALYST, not content generator
-- 💬 FOCUS on industry/domain analysis with verified sources
+
+- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions
+- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding
+- ✅ ALWAYS use {{current_year}} web searches for current industry data
+- 📋 YOU ARE AN INDUSTRY ANALYST, not content generator
+- 💬 FOCUS on market size, growth, and industry dynamics
 - 🔍 WEB RESEARCH REQUIRED - Use {{current_year}} data and verify sources
+- 📝 WRITE CONTENT IMMEDIATELY TO DOCUMENT
 
 ## EXECUTION PROTOCOLS:
 
 - 🎯 Show web search analysis before presenting findings
-- ⚠️ Present [C] continue option after domain analysis content generation
-- 💾 ONLY save when user chooses C (Continue)
+- ⚠️ Present [C] continue option after industry analysis content generation
+- 📝 WRITE INDUSTRY ANALYSIS TO DOCUMENT IMMEDIATELY
+- 💾 ONLY proceed when user chooses C (Continue)
 - 📖 Update frontmatter `stepsCompleted: [1, 2]` before loading next step
 - 🚫 FORBIDDEN to load next step until C is selected
 
 ## CONTEXT BOUNDARIES:
 
 - Current document and frontmatter from step-01 are available
-- Research type = "domain" is already set
-- Focus on industry/domain web research with {{current_year}} data
+- **Research topic = "{{research_topic}}"** - established from initial discussion
+- **Research goals = "{{research_goals}}"** - established from initial discussion
+- Focus on market size, growth, and industry dynamics
 - Web search capabilities with source verification are enabled
 
 ## YOUR TASK:
 
-Conduct comprehensive domain/industry analysis using current {{current_year}} web data with rigorous source verification.
+Conduct industry analysis focusing on market size, growth, and industry dynamics using current {{current_year}} web data with rigorous source verification.
 
-## DOMAIN ANALYSIS SEQUENCE:
+## INDUSTRY ANALYSIS SEQUENCE:
 
-### 1. Begin Domain Analysis
+### 1. Begin Industry Analysis
 
-**UTILIZE SUBPROCESSES AND SUBAGENTS**: Use research subagents, subprocesses or parallel processing if available to thoroughly analyze different domain areas simultaneously and thoroughly
+**UTILIZE SUBPROCESSES AND SUBAGENTS**: Use research subagents, subprocesses or parallel processing if available to thoroughly analyze different industry areas simultaneously and thoroughly.
 
-Start with web research approach:
-"Now I'll conduct comprehensive domain research using current {{current_year}} web data with rigorous source verification.
+Start with industry research approach:
+"Now I'll conduct **industry analysis** for **{{research_topic}}** using current {{current_year}} web data to understand market dynamics.
 
-**Domain Analysis Focus:**
+**Industry Analysis Focus:**
 
-- Industry size, growth, and market dynamics
-- Technology trends and innovation patterns
-- Regulatory landscape and compliance requirements
-- Key players and competitive ecosystem
-- Supply chain and business model evolution
+- Market size and valuation metrics
+- Growth rates and market dynamics
+- Market segmentation and structure
+- Industry trends and evolution patterns
+- Economic impact and value creation
 
-**Let me search for current {{current_year}} data on [domain/industry] using parallel web searches for comprehensive coverage.**"
+**Let me search for current industry insights.**"
 
-### 2. Parallel Web Search Execution
+### 2. Parallel Industry Research Execution
 
 **Execute multiple web searches simultaneously:**
 
-`WebSearch: "[domain/industry] market size growth {{current_year}}"`
-`WebSearch: "[domain/industry] technology trends {{current_year}}"`
-`WebSearch: "[domain/industry] regulations compliance {{current_year}}"`
-`WebSearch: "[domain/industry] key players ecosystem {{current_year}}"`
+`WebSearch: "{{research_topic}} market size value {{current_year}}"`
+`WebSearch: "{{research_topic}} market growth rate dynamics {{current_year}}"`
+`WebSearch: "{{research_topic}} market segmentation structure {{current_year}}"`
+`WebSearch: "{{research_topic}} industry trends evolution {{current_year}}"`
 
 **Analysis approach:**
 
 - Look for recent market research reports and industry analyses
-- Identify market size, growth rates, and trends
-- Find authoritative sources (market research firms, industry associations)
-- Note conflicting information from different sources
-- Gather technology trends and innovation patterns
-- Research regulatory requirements and compliance standards
-- Analyze competitive landscape and key players
+- Search for authoritative sources (market research firms, industry associations)
+- Identify market size, growth rates, and segmentation data
+- Research industry trends and evolution patterns
+- Analyze economic impact and value creation metrics
 
 ### 3. Analyze and Aggregate Results
 
 **Collect and analyze findings from all parallel searches:**
 
-"After executing comprehensive parallel web searches, let me analyze and aggregate the findings:
+"After executing comprehensive parallel web searches, let me analyze and aggregate industry findings:
 
 **Research Coverage:**
 
-- Market analysis and industry dynamics
-- Technology trends and innovation patterns
-- Regulatory landscape and compliance requirements
-- Key players and competitive ecosystem
+- Market size and valuation analysis
+- Growth rates and market dynamics
+- Market segmentation and structure
+- Industry trends and evolution patterns
 
-**Cross-Domain Analysis:**
-[Identify patterns, connections, and insights that emerge across multiple search areas]
+**Cross-Industry Analysis:**
+[Identify patterns connecting market dynamics, segmentation, and trends]
 
 **Quality Assessment:**
 [Overall confidence levels and research gaps identified]"
 
-### 4. Generate Domain Analysis Content
+### 4. Generate Industry Analysis Content
 
-Prepare analysis content with source citations:
+**WRITE IMMEDIATELY TO DOCUMENT**
+
+Prepare industry analysis with web search citations:
 
 #### Content Structure:
 
 When saving to document, append these Level 2 and Level 3 sections:
 
 ```markdown
-## Industry Overview
+## Industry Analysis
 
-### Market Size and Growth
+### Market Size and Valuation
 
-[Market size and growth data with source citations]
-_Source: [URL with {{current_year}} data]_
+[Market size analysis with source citations]
+_Total Market Size: [Current market valuation with {{current_year}} data]_
+_Growth Rate: [CAGR and market growth projections]_
+_Market Segments: [Size and value of key market segments]_
+_Economic Impact: [Economic contribution and value creation]_
+_Source: [URL with {{current_year}} market size data]_
 
-### Technology Trends
+### Market Dynamics and Growth
 
-[Technology trends analysis with source citations]
-_Source: [URL with {{current_year}} data]_
+[Market dynamics analysis with source citations]
+_Growth Drivers: [Key factors driving market growth]_
+_Growth Barriers: [Factors limiting market expansion]_
+_Cyclical Patterns: [Industry seasonality and cycles]_
+_Market Maturity: [Life cycle stage and development phase]_
+_Source: [URL with {{current_year}} market dynamics data]_
 
-### Regulatory Landscape
+### Market Structure and Segmentation
 
-[Regulatory analysis with source citations]
-_Source: [URL with {{current_year}} data]_
+[Market structure analysis with source citations]
+_Primary Segments: [Key market segments and their characteristics]_
+_Sub-segment Analysis: [Detailed breakdown of market sub-segments]_
+_Geographic Distribution: [Regional market variations and concentrations]_
+_Vertical Integration: [Supply chain and value chain structure]_
+_Source: [URL with {{current_year}} market structure data]_
 
-### Key Players and Ecosystem
+### Industry Trends and Evolution
 
-[Key players analysis with source citations]
-_Source: [URL with {{current_year}} data]_
+[Industry trends analysis with source citations]
+_Emerging Trends: [Current industry developments and transformations]_
+_Historical Evolution: [Industry development over recent years]_
+_Technology Integration: [How technology is changing the industry]_
+_Future Outlook: [Projected industry developments and changes]_
+_Source: [URL with {{current_year}} industry trends data]_
 
-### Growth Drivers and Challenges
+### Competitive Dynamics
 
-[Growth drivers and challenges with source citations]
-_Source: [URL with {{current_year}} data]_
+[Competitive dynamics analysis with source citations]
+_Market Concentration: [Level of market consolidation and competition]_
+_Competitive Intensity: [Degree of competition and rivalry]_
+_Barriers to Entry: [Obstacles for new market entrants]_
+_Innovation Pressure: [Rate of innovation and change]_
+_Source: [URL with {{current_year}} competitive dynamics data]_
 ```
 
 ### 5. Present Analysis and Continue Option
 
-Show the generated analysis and present continue option:
-"I've completed the **domain/industry analysis** using current {{current_year}} web data with rigorous source verification.
+**Show analysis and present continue option:**
 
-**Key Findings:**
+"I've completed **industry analysis** using current {{current_year}} data to understand market dynamics for {{research_topic}}.
 
-- Multiple sources verified for critical market data
-- Conflicting information noted where sources disagree
-- Confidence levels applied to uncertain data
-- All factual claims include source citations
+**Key Industry Findings:**
 
-**Ready to proceed to regulatory focus?**
-[C] Continue - Save this to the document and move to regulatory focus
+- Market size and valuation thoroughly analyzed
+- Growth dynamics and market structure documented
+- Industry trends and evolution patterns identified
+- Competitive dynamics clearly mapped
+- Multiple sources verified for critical insights
+
+**Ready to proceed to competitive landscape analysis?**
+[C] Continue - Save this to document and proceed to competitive landscape
 
 ### 6. Handle Continue Selection
 
 #### If 'C' (Continue):
 
-- Append the final content to the research document
+- **CONTENT ALREADY WRITTEN TO DOCUMENT**
 - Update frontmatter: `stepsCompleted: [1, 2]`
-- Load: `./step-03-regulatory-focus.md`
+- Load: `./step-03-competitive-landscape.md`
 
 ## APPEND TO DOCUMENT:
 
-When user selects 'C', append the content directly to the research document using the structure from step 4.
+Content is already written to document when generated in step 4. No additional append needed.
 
 ## SUCCESS METRICS:
 
-✅ Industry size and growth data with current {{current_year}} citations
-✅ Technology trends identified with current developments
-✅ Regulatory landscape analysis with current requirements
-✅ Key players and ecosystem mapped with current data
+✅ Market size and valuation thoroughly analyzed
+✅ Growth dynamics and market structure documented
+✅ Industry trends and evolution patterns identified
+✅ Competitive dynamics clearly mapped
+✅ Multiple sources verified for critical insights
+✅ Content written immediately to document
 ✅ [C] continue option presented and handled correctly
-✅ Content properly appended to document when C selected
-✅ Web searches properly structured with {{current_year}} parameter
+✅ Proper routing to next step (competitive landscape)
+✅ Research goals alignment maintained
 
 ## FAILURE MODES:
 
-❌ Not using {{current_year}} in web search queries
-❌ Not requiring source citations for factual claims
-❌ Not presenting conflicting information when sources disagree
-❌ Not applying confidence levels to uncertain data
+❌ Not using {{current_year}} in industry web searches
+❌ Missing critical market size or growth data
+❌ Incomplete market structure analysis
+❌ Not identifying key industry trends
+❌ Not writing content immediately to document
 ❌ Not presenting [C] continue option after content generation
-❌ Appending content without user selecting 'C'
+❌ Not routing to competitive landscape step
 
-## WEB RESEARCH PROTOCOLS:
+❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions
+❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file
+❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols
 
-All web searches must:
+## INDUSTRY RESEARCH PROTOCOLS:
 
-- Include {{current_year}} for current data
-- Require multiple sources for critical claims
-- Present conflicting information when found
-- Include source URLs for all factual claims
+- Research market research reports and industry analyses
+- Use authoritative sources (market research firms, industry associations)
+- Analyze market size, growth rates, and segmentation data
+- Study industry trends and evolution patterns
+- Focus on current {{current_year}} industry data
+- Present conflicting information when sources disagree
 - Apply confidence levels appropriately
 
-## SOURCE VERIFICATION:
+## INDUSTRY ANALYSIS STANDARDS:
 
 - Always cite URLs for web search results
-- Use authoritative sources (market research firms, industry associations)
+- Use authoritative industry research sources
 - Note data currency and potential limitations
 - Present multiple perspectives when sources conflict
+- Apply confidence levels to uncertain data
+- Focus on actionable industry insights
 
 ## NEXT STEP:
 
-After user selects 'C' and content is saved to document, load `./step-03-regulatory-focus.md` to focus on specific regulatory and compliance requirements.
+After user selects 'C', load `./step-03-competitive-landscape.md` to analyze competitive landscape, key players, and ecosystem analysis for {{research_topic}}.
 
-Remember: Always emphasize current {{current_year}} data and rigorous source verification in domain research!
+Remember: Always write research content to document immediately and emphasize current {{current_year}} industry data with rigorous source verification!

src/modules/bmm/workflows/1-analysis/research/domain-steps/step-03-competitive-landscape.md

@@ -0,0 +1,237 @@
+# Domain Research Step 3: Competitive Landscape
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+- 🛑 NEVER generate content without web search verification
+
+- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions
+- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding
+- ✅ ALWAYS use {{current_year}} web searches for current competitive data
+- 📋 YOU ARE A COMPETITIVE ANALYST, not content generator
+- 💬 FOCUS on key players, market share, and competitive dynamics
+- 🔍 WEB RESEARCH REQUIRED - Use {{current_year}} data and verify sources
+- 📝 WRITE CONTENT IMMEDIATELY TO DOCUMENT
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Show web search analysis before presenting findings
+- ⚠️ Present [C] continue option after competitive analysis content generation
+- 📝 WRITE COMPETITIVE ANALYSIS TO DOCUMENT IMMEDIATELY
+- 💾 ONLY proceed when user chooses C (Continue)
+- 📖 Update frontmatter `stepsCompleted: [1, 2, 3]` before loading next step
+- 🚫 FORBIDDEN to load next step until C is selected
+
+## CONTEXT BOUNDARIES:
+
+- Current document and frontmatter from previous steps are available
+- **Research topic = "{{research_topic}}"** - established from initial discussion
+- **Research goals = "{{research_goals}}"** - established from initial discussion
+- Focus on key players, market share, and competitive dynamics
+- Web search capabilities with source verification are enabled
+
+## YOUR TASK:
+
+Conduct competitive landscape analysis focusing on key players, market share, and competitive dynamics using current {{current_year}} web data with rigorous source verification.
+
+## COMPETITIVE LANDSCAPE ANALYSIS SEQUENCE:
+
+### 1. Begin Competitive Landscape Analysis
+
+**UTILIZE SUBPROCESSES AND SUBAGENTS**: Use research subagents, subprocesses or parallel processing if available to thoroughly analyze different competitive areas simultaneously and thoroughly.
+
+Start with competitive research approach:
+"Now I'll conduct **competitive landscape analysis** for **{{research_topic}}** using current {{current_year}} web data to understand the competitive ecosystem.
+
+**Competitive Landscape Focus:**
+
+- Key players and market leaders
+- Market share and competitive positioning
+- Competitive strategies and differentiation
+- Business models and value propositions
+- Entry barriers and competitive dynamics
+
+**Let me search for current competitive insights.**"
+
+### 2. Parallel Competitive Research Execution
+
+**Execute multiple web searches simultaneously:**
+
+`WebSearch: "{{research_topic}} key players market leaders {{current_year}}"`
+`WebSearch: "{{research_topic}} market share competitive landscape {{current_year}}"`
+`WebSearch: "{{research_topic}} competitive strategies differentiation {{current_year}}"`
+`WebSearch: "{{research_topic}} entry barriers competitive dynamics {{current_year}}"`
+
+**Analysis approach:**
+
+- Look for recent competitive intelligence reports and market analyses
+- Search for company websites, annual reports, and investor presentations
+- Research market share data and competitive positioning
+- Analyze competitive strategies and differentiation approaches
+- Study entry barriers and competitive dynamics
+
+### 3. Analyze and Aggregate Results
+
+**Collect and analyze findings from all parallel searches:**
+
+"After executing comprehensive parallel web searches, let me analyze and aggregate competitive findings:
+
+**Research Coverage:**
+
+- Key players and market leaders analysis
+- Market share and competitive positioning assessment
+- Competitive strategies and differentiation mapping
+- Entry barriers and competitive dynamics evaluation
+
+**Cross-Competitive Analysis:**
+[Identify patterns connecting players, strategies, and market dynamics]
+
+**Quality Assessment:**
+[Overall confidence levels and research gaps identified]"
+
+### 4. Generate Competitive Landscape Content
+
+**WRITE IMMEDIATELY TO DOCUMENT**
+
+Prepare competitive landscape analysis with web search citations:
+
+#### Content Structure:
+
+When saving to document, append these Level 2 and Level 3 sections:
+
+```markdown
+## Competitive Landscape
+
+### Key Players and Market Leaders
+
+[Key players analysis with source citations]
+_Market Leaders: [Dominant players and their market positions]_
+_Major Competitors: [Significant competitors and their specialties]_
+_Emerging Players: [New entrants and innovative companies]_
+_Global vs Regional: [Geographic distribution of key players]_
+_Source: [URL with {{current_year}} competitive data]_
+
+### Market Share and Competitive Positioning
+
+[Market share analysis with source citations]
+_Market Share Distribution: [Current market share breakdown]_
+_Competitive Positioning: [How players position themselves in the market]_
+_Value Proposition Mapping: [Different value propositions across players]_
+_Customer Segments Served: [Different customer bases by competitor]_
+_Source: [URL with {{current_year}} market share data]_
+
+### Competitive Strategies and Differentiation
+
+[Competitive strategies analysis with source citations]
+_Cost Leadership Strategies: [Players competing on price and efficiency]_
+_Differentiation Strategies: [Players competing on unique value]_
+_Focus/Niche Strategies: [Players targeting specific segments]_
+_Innovation Approaches: [How different players innovate]_
+_Source: [URL with {{current_year}} competitive strategies data]_
+
+### Business Models and Value Propositions
+
+[Business models analysis with source citations]
+_Primary Business Models: [How competitors make money]_
+_Revenue Streams: [Different approaches to monetization]_
+_Value Chain Integration: [Vertical integration vs partnership models]_
+_Customer Relationship Models: [How competitors build customer loyalty]_
+_Source: [URL with {{current_year}} business models data]_
+
+### Competitive Dynamics and Entry Barriers
+
+[Competitive dynamics analysis with source citations]
+_Barriers to Entry: [Obstacles facing new market entrants]_
+_Competitive Intensity: [Level of rivalry and competitive pressure]_
+_Market Consolidation Trends: [M&A activity and market concentration]_
+_Switching Costs: [Costs for customers to switch between providers]_
+_Source: [URL with {{current_year}} competitive dynamics data]_
+
+### Ecosystem and Partnership Analysis
+
+[Ecosystem analysis with source citations]
+_Supplier Relationships: [Key supplier partnerships and dependencies]_
+_Distribution Channels: [How competitors reach customers]_
+_Technology Partnerships: [Strategic technology alliances]_
+_Ecosystem Control: [Who controls key parts of the value chain]_
+_Source: [URL with {{current_year}} ecosystem data]_
+```
+
+### 5. Present Analysis and Continue Option
+
+**Show analysis and present continue option:**
+
+"I've completed **competitive landscape analysis** using current {{current_year}} data to understand the competitive ecosystem for {{research_topic}}.
+
+**Key Competitive Findings:**
+
+- Key players and market leaders thoroughly identified
+- Market share and competitive positioning clearly mapped
+- Competitive strategies and differentiation analyzed
+- Business models and value propositions documented
+- Competitive dynamics and entry barriers evaluated
+
+**Ready to proceed to regulatory focus analysis?**
+[C] Continue - Save this to document and proceed to regulatory focus
+
+### 6. Handle Continue Selection
+
+#### If 'C' (Continue):
+
+- **CONTENT ALREADY WRITTEN TO DOCUMENT**
+- Update frontmatter: `stepsCompleted: [1, 2, 3]`
+- Load: `./step-04-regulatory-focus.md`
+
+## APPEND TO DOCUMENT:
+
+Content is already written to document when generated in step 4. No additional append needed.
+
+## SUCCESS METRICS:
+
+✅ Key players and market leaders thoroughly identified
+✅ Market share and competitive positioning clearly mapped
+✅ Competitive strategies and differentiation analyzed
+✅ Business models and value propositions documented
+✅ Competitive dynamics and entry barriers evaluated
+✅ Content written immediately to document
+✅ [C] continue option presented and handled correctly
+✅ Proper routing to next step (regulatory focus)
+✅ Research goals alignment maintained
+
+## FAILURE MODES:
+
+❌ Not using {{current_year}} in competitive web searches
+❌ Missing critical key players or market leaders
+❌ Incomplete market share or positioning analysis
+❌ Not identifying competitive strategies
+❌ Not writing content immediately to document
+❌ Not presenting [C] continue option after content generation
+❌ Not routing to regulatory focus step
+
+❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions
+❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file
+❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols
+
+## COMPETITIVE RESEARCH PROTOCOLS:
+
+- Research competitive intelligence reports and market analyses
+- Use company websites, annual reports, and investor presentations
+- Analyze market share data and competitive positioning
+- Study competitive strategies and differentiation approaches
+- Focus on current {{current_year}} competitive data
+- Present conflicting information when sources disagree
+- Apply confidence levels appropriately
+
+## COMPETITIVE ANALYSIS STANDARDS:
+
+- Always cite URLs for web search results
+- Use authoritative competitive intelligence sources
+- Note data currency and potential limitations
+- Present multiple perspectives when sources conflict
+- Apply confidence levels to uncertain data
+- Focus on actionable competitive insights
+
+## NEXT STEP:
+
+After user selects 'C', load `./step-04-regulatory-focus.md` to analyze regulatory requirements, compliance frameworks, and legal considerations for {{research_topic}}.
+
+Remember: Always write research content to document immediately and emphasize current {{current_year}} competitive data with rigorous source verification!

src/modules/bmm/workflows/1-analysis/research/domain-steps/step-04-regulatory-focus.md

@@ -1,38 +1,44 @@
-# Domain Research Step 3: Regulatory Focus
+# Domain Research Step 4: Regulatory Focus
 
 ## MANDATORY EXECUTION RULES (READ FIRST):
 
 - 🛑 NEVER generate content without web search verification
+
+- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions
+- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding
 - ✅ ALWAYS use {{current_year}} web searches for current regulatory data
 - 📋 YOU ARE A REGULATORY ANALYST, not content generator
 - 💬 FOCUS on compliance requirements and regulatory landscape
 - 🔍 WEB RESEARCH REQUIRED - Use {{current_year}} data and verify sources
+- 📝 WRITE CONTENT IMMEDIATELY TO DOCUMENT
 
 ## EXECUTION PROTOCOLS:
 
 - 🎯 Show web search analysis before presenting findings
 - ⚠️ Present [C] continue option after regulatory content generation
+- 📝 WRITE REGULATORY ANALYSIS TO DOCUMENT IMMEDIATELY
 - 💾 ONLY save when user chooses C (Continue)
-- 📖 Update frontmatter `stepsCompleted: [1, 2, 3]` before loading next step
+- 📖 Update frontmatter `stepsCompleted: [1, 2, 3, 4]` before loading next step
 - 🚫 FORBIDDEN to load next step until C is selected
 
 ## CONTEXT BOUNDARIES:
 
 - Current document and frontmatter from previous steps are available
+- **Research topic = "{{research_topic}}"** - established from initial discussion
+- **Research goals = "{{research_goals}}"** - established from initial discussion
 - Focus on regulatory and compliance requirements for the domain
 - Web search capabilities with source verification are enabled
-- May need to search for specific regulations and compliance frameworks
 
 ## YOUR TASK:
 
-Conduct focused regulatory and compliance analysis using current {{current_year}} web data with emphasis on requirements that impact your project.
+Conduct focused regulatory and compliance analysis using current {{current_year}} web data with emphasis on requirements that impact {{research_topic}}.
 
 ## REGULATORY FOCUS SEQUENCE:
 
 ### 1. Begin Regulatory Analysis
 
 Start with regulatory research approach:
-"Now I'll focus on **regulatory and compliance requirements** that impact the [domain/industry] using current {{current_year}} data.
+"Now I'll focus on **regulatory and compliance requirements** that impact **{{research_topic}}** using current {{current_year}} data.
 
 **Regulatory Focus Areas:**
 
@@ -47,7 +53,7 @@ Start with regulatory research approach:
 ### 2. Web Search for Specific Regulations
 
 Search for current regulatory information:
-`WebSearch: "[domain/industry] regulations compliance requirements {{current_year}}"`
+`WebSearch: "{{research_topic}} regulations compliance requirements {{current_year}}"`
 
 **Regulatory focus:**
 
@@ -59,7 +65,7 @@ Search for current regulatory information:
 ### 3. Web Search for Industry Standards
 
 Search for current industry standards:
-`WebSearch: "[domain/industry] standards best practices {{current_year}}"`
+`WebSearch: "{{research_topic}} standards best practices {{current_year}}"`
 
 **Standards focus:**
 
@@ -71,7 +77,7 @@ Search for current industry standards:
 ### 4. Web Search for Data Privacy Requirements
 
 Search for current privacy regulations:
-`WebSearch: "data privacy regulations [domain/industry] {{current_year}}"`
+`WebSearch: "data privacy regulations {{research_topic}} {{current_year}}"`
 
 **Privacy focus:**
 
@@ -129,7 +135,7 @@ _Source: [URL with {{current_year}} implementation data]_
 ### 6. Present Analysis and Continue Option
 
 Show the generated regulatory analysis and present continue option:
-"I've completed the **regulatory requirements analysis** focusing on compliance requirements that impact your [domain/industry] project.
+"I've completed **regulatory requirements analysis** using current {{current_year}} data to understand compliance requirements for {{research_topic}}.
 
 **Key Regulatory Findings:**
 
@@ -146,13 +152,13 @@ Show the generated regulatory analysis and present continue option:
 
 #### If 'C' (Continue):
 
-- Append the final content to the research document
-- Update frontmatter: `stepsCompleted: [1, 2, 3]`
-- Load: `./step-04-technical-trends.md`
+- **CONTENT ALREADY WRITTEN TO DOCUMENT**
+- Update frontmatter: `stepsCompleted: [1, 2, 3, 4]`
+- Load: `./step-05-technical-trends.md`
 
 ## APPEND TO DOCUMENT:
 
-When user selects 'C', append the content directly to the research document using the structure from step 5.
+Content is already written to document when generated in step 5. No additional append needed.
 
 ## SUCCESS METRICS:
 
@@ -173,6 +179,10 @@ When user selects 'C', append the content directly to the research document usin
 ❌ Not presenting [C] continue option after content generation
 ❌ Appending content without user selecting 'C'
 
+❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions
+❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file
+❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols
+
 ## REGULATORY RESEARCH PROTOCOLS:
 
 - Search for specific regulations by name and number

src/modules/bmm/workflows/1-analysis/research/domain-steps/step-05-technical-trends.md

@@ -1,38 +1,44 @@
-# Domain Research Step 4: Technical Trends
+# Domain Research Step 5: Technical Trends
 
 ## MANDATORY EXECUTION RULES (READ FIRST):
 
 - 🛑 NEVER generate content without web search verification
+
+- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions
+- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding
 - ✅ ALWAYS use {{current_year}} web searches for current technical data
 - 📋 YOU ARE A TECHNOLOGY ANALYST, not content generator
 - 💬 FOCUS on emerging technologies and innovation patterns
 - 🔍 WEB RESEARCH REQUIRED - Use {{current_year}} data and verify sources
+- 📝 WRITE CONTENT IMMEDIATELY TO DOCUMENT
 
 ## EXECUTION PROTOCOLS:
 
 - 🎯 Show web search analysis before presenting findings
-- ⚠️ Present [C] complete option after technical trends content generation
-- 💾 ONLY save when user chooses C (Complete)
-- 📖 Update frontmatter `stepsCompleted: [1, 2, 3, 4]` before completing workflow
-- 🚫 FORBIDDEN to complete workflow until C is selected
+- ⚠️ Present [C] continue option after technical trends content generation
+- 📝 WRITE TECHNICAL TRENDS ANALYSIS TO DOCUMENT IMMEDIATELY
+- 💾 ONLY proceed when user chooses C (Continue)
+- 📖 Update frontmatter `stepsCompleted: [1, 2, 3, 4, 5]` before loading next step
+- 🚫 FORBIDDEN to load next step until C is selected
 
 ## CONTEXT BOUNDARIES:
 
 - Current document and frontmatter from previous steps are available
+- **Research topic = "{{research_topic}}"** - established from initial discussion
+- **Research goals = "{{research_goals}}"** - established from initial discussion
 - Focus on emerging technologies and innovation patterns in the domain
 - Web search capabilities with source verification are enabled
-- This is the final step in the domain research workflow
 
 ## YOUR TASK:
 
-Conduct comprehensive technical trends analysis using current {{current_year}} web data with emphasis on innovations and emerging technologies impacting the domain.
+Conduct comprehensive technical trends analysis using current {{current_year}} web data with emphasis on innovations and emerging technologies impacting {{research_topic}}.
 
 ## TECHNICAL TRENDS SEQUENCE:
 
 ### 1. Begin Technical Trends Analysis
 
 Start with technology research approach:
-"Now I'll complete our domain research with **technical trends and emerging technologies** analysis using current {{current_year}} data.
+"Now I'll conduct **technical trends and emerging technologies** analysis for **{{research_topic}}** using current {{current_year}} data.
 
 **Technical Trends Focus:**
 
@@ -47,7 +53,7 @@ Start with technology research approach:
 ### 2. Web Search for Emerging Technologies
 
 Search for current technology information:
-`WebSearch: "[domain/industry] emerging technologies innovations {{current_year}}"`
+`WebSearch: "{{research_topic}} emerging technologies innovations {{current_year}}"`
 
 **Technology focus:**
 
@@ -59,7 +65,7 @@ Search for current technology information:
 ### 3. Web Search for Digital Transformation
 
 Search for current transformation trends:
-`WebSearch: "[domain/industry] digital transformation {{current_year}}"`
+`WebSearch: "{{research_topic}} digital transformation {{current_year}}"`
 
 **Transformation focus:**
 
@@ -71,7 +77,7 @@ Search for current transformation trends:
 ### 4. Web Search for Future Outlook
 
 Search for future projections:
-`WebSearch: "[domain/industry] future outlook {{current_year}} 2025"`
+`WebSearch: "{{research_topic}} future outlook {{current_year}} 2025"`
 
 **Future focus:**
 
@@ -82,6 +88,8 @@ Search for future projections:
 
 ### 5. Generate Technical Trends Content
 
+**WRITE IMMEDIATELY TO DOCUMENT**
+
 Prepare technical analysis with source citations:
 
 #### Content Structure:
@@ -139,7 +147,7 @@ _Source: [URL with {{current_year}} risk data]_
 ### 6. Present Analysis and Complete Option
 
 Show the generated technical analysis and present complete option:
-"I've completed the **technical trends and innovation analysis** using current {{current_year}} data, finalizing our comprehensive domain research.
+"I've completed **technical trends and innovation analysis** using current {{current_year}} data to understand technology patterns for {{research_topic}}.
 
 **Technical Highlights:**
 
@@ -149,27 +157,27 @@ Show the generated technical analysis and present complete option:
 - Implementation opportunities and challenges documented
 - Practical recommendations provided
 
-**This completes our domain research covering:**
+**Technical Trends Research Completed:**
 
-- Industry overview and market dynamics
-- Regulatory requirements and compliance
-- Technical trends and innovations
-- Strategic recommendations for your project
+- Emerging technologies and innovations identified
+- Digital transformation trends mapped
+- Future outlook and projections analyzed
+- Implementation opportunities and challenges documented
 
-**Ready to complete the domain research report?**
-[C] Complete Research - Save final document and conclude
+**Ready to proceed to research synthesis and recommendations?**
+[C] Continue - Save this to document and proceed to synthesis
 
-### 7. Handle Complete Selection
+### 7. Handle Continue Selection
 
-#### If 'C' (Complete Research):
+#### If 'C' (Continue):
 
-- Append the final content to the research document
-- Update frontmatter: `stepsCompleted: [1, 2, 3, 4]`
-- Complete the domain research workflow
+- **CONTENT ALREADY WRITTEN TO DOCUMENT**
+- Update frontmatter: `stepsCompleted: [1, 2, 3, 4, 5]`
+- Load: `./step-06-research-synthesis.md`
 
 ## APPEND TO DOCUMENT:
 
-When user selects 'C', append the content directly to the research document using the structure from step 5.
+Content is already written to document when generated in step 5. No additional append needed.
 
 ## SUCCESS METRICS:
 
@@ -178,9 +186,10 @@ When user selects 'C', append the content directly to the research document usin
 ✅ Future outlook and projections analyzed
 ✅ Implementation opportunities and challenges mapped
 ✅ Strategic recommendations provided
-✅ [C] complete option presented and handled correctly
-✅ Content properly appended to document when C selected
-✅ Research workflow completed successfully
+✅ Content written immediately to document
+✅ [C] continue option presented and handled correctly
+✅ Proper routing to next step (research synthesis)
+✅ Research goals alignment maintained
 
 ## FAILURE MODES:
 
@@ -191,6 +200,10 @@ When user selects 'C', append the content directly to the research document usin
 ❌ Not presenting completion option for research workflow
 ❌ Appending content without user selecting 'C'
 
+❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions
+❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file
+❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols
+
 ## TECHNICAL RESEARCH PROTOCOLS:
 
 - Search for cutting-edge technologies and innovations

src/modules/bmm/workflows/1-analysis/research/domain-steps/step-06-research-synthesis.md

@@ -1,8 +1,11 @@
-# Domain Research Step 5: Research Synthesis and Completion
+# Domain Research Step 6: Research Synthesis and Completion
 
 ## MANDATORY EXECUTION RULES (READ FIRST):
 
 - 🛑 NEVER generate content without web search verification
+
+- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions
+- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding
 - ✅ ALWAYS use {{current_year}} web searches for current domain data
 - 📋 YOU ARE A DOMAIN RESEARCH STRATEGIST, not content generator
 - 💬 FOCUS on comprehensive synthesis and authoritative conclusions
@@ -14,7 +17,7 @@
 - 🎯 Show web search analysis before presenting findings
 - ⚠️ Present [C] complete option after synthesis content generation
 - 💾 ONLY save when user chooses C (Complete)
-- 📖 Update frontmatter `stepsCompleted: [1, 2, 3, 4, 5]` before completing workflow
+- 📖 Update frontmatter `stepsCompleted: [1, 2, 3, 4, 5, 6]` before completing workflow
 - 🚫 FORBIDDEN to complete workflow until C is selected
 - 📚 GENERATE COMPLETE DOCUMENT STRUCTURE with intro, TOC, and summary
 
@@ -402,6 +405,10 @@ When user selects 'C', append the complete comprehensive research document using
 ❌ Producing document without professional structure
 ❌ Not presenting completion option for final document
 
+❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions
+❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file
+❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols
+
 ## COMPREHENSIVE DOCUMENT STANDARDS:
 
 This step ensures the final research document:

src/modules/bmm/workflows/1-analysis/research/market-steps/step-01-init.md

@@ -1,18 +1,20 @@
-# Market Research Step 1: Market Analysis
+# Market Research Step 1: Market Research Initialization
 
 ## MANDATORY EXECUTION RULES (READ FIRST):
 
-- 🛑 NEVER generate content without web search verification
-- ✅ ALWAYS use {{current_year}} web searches for current market data
-- 📋 YOU ARE A MARKET ANALYST, not content generator
-- 💬 FOCUS on market size, growth, and competitive analysis
-- 🔍 WEB RESEARCH REQUIRED - Use {{current_year}} data and verify sources
+- 🛑 NEVER generate research content in init step
+- ✅ ALWAYS confirm understanding of user's research goals
+- 📋 YOU ARE A MARKET RESEARCH FACILITATOR, not content generator
+- 💬 FOCUS on clarifying scope and approach
+- 🔍 NO WEB RESEARCH in init - that's for later steps
+- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete research
+- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding
 
 ## EXECUTION PROTOCOLS:
 
-- 🎯 Show web search analysis before presenting findings
-- ⚠️ Present [C] continue option after market analysis content generation
-- 💾 ONLY save when user chooses C (Continue)
+- 🎯 Confirm research understanding before proceeding
+- ⚠️ Present [C] continue option after scope clarification
+- 💾 Write initial scope document immediately
 - 📖 Update frontmatter `stepsCompleted: [1]` before loading next step
 - 🚫 FORBIDDEN to load next step until C is selected
 
@@ -22,144 +24,159 @@
 - Research type = "market" is already set
 - **Research topic = "{{research_topic}}"** - discovered from initial discussion
 - **Research goals = "{{research_goals}}"** - captured from initial discussion
-- Focus on market research with current {{current_year}} data
-- Web search capabilities with source verification are enabled
+- Focus on market research scope clarification
+- Web search capabilities are enabled for later steps
 
 ## YOUR TASK:
 
-Initialize market research scope and approach for the already-identified topic: **{{research_topic}}** with goals: {{research_goals}}
+Initialize market research by confirming understanding of {{research_topic}} and establishing clear research scope.
 
-## MARKET ANALYSIS SEQUENCE:
+## MARKET RESEARCH INITIALIZATION:
 
-### 1. Initialize Market Research
+### 1. Confirm Research Understanding
 
-Start with market-specific positioning:
-"I'll guide you through **market research** for **{{research_topic}}** using current {{current_year}} web data with rigorous source verification.
+**INITIALIZE - DO NOT RESEARCH YET**
 
-**Research Goals Identified:** {{research_goals}}
+Start with research confirmation:
+"I understand you want to conduct **market research** for **{{research_topic}}** with these goals: {{research_goals}}
 
-**Market Research Focus for {{research_topic}}:**
+**My Understanding of Your Research Needs:**
 
-- Market size and growth projections for {{research_topic}}
-- Customer segments and demographics interested in {{research_topic}}
-- Competitive landscape analysis in {{research_topic}} market
-- Pricing strategies and business models for {{research_topic}}
-- Market trends and consumer behavior around {{research_topic}}
+- **Research Topic**: {{research_topic}}
+- **Research Goals**: {{research_goals}}
+- **Research Type**: Market Research using current {{current_year}} data
+- **Approach**: Comprehensive market analysis with rigorous source verification
 
-Let me refine the market research scope specifically for **{{research_topic}}**:
+**Market Research Areas We'll Cover:**
 
-### 2. Establish Market Research Context
+- Market size, growth dynamics, and trends
+- Customer insights and behavior analysis
+- Competitive landscape and positioning
+- Strategic recommendations and implementation guidance
 
-#### Market Context Questions:
+**Does this accurately capture what you're looking for?**"
 
-- "What specific market aspects of {{research_topic}} are most critical for your goals?"
-- "Are there particular customer segments or demographics within {{research_topic}} we should focus on?"
-- "Should we analyze the global {{research_topic}} market or specific regions?"
-- "What time horizon for {{research_topic}} market research - current state or future projections?"
-- "How comprehensive should the {{research_topic}} competitive analysis be?"
+### 2. Refine Research Scope
 
-### 3. Begin Market Research Execution
+Gather any clarifications needed:
 
-After scope refinement, proceed with:
+#### Scope Clarification Questions:
 
-### 2. Generate Market Analysis Content
+- "Are there specific customer segments or aspects of {{research_topic}} we should prioritize?"
+- "Should we focus on specific geographic regions or global market?"
+- "Is this for market entry, expansion, product development, or other business purpose?"
+- "Any competitors or market segments you specifically want us to analyze?"
 
-Prepare market analysis with web search citations:
+### 3. Document Initial Scope
 
-#### Content Structure:
+**WRITE IMMEDIATELY TO DOCUMENT**
 
-When saving to document, append these Level 2 and Level 3 sections:
+Write initial research scope to document:
 
 ```markdown
-## Market Analysis
+# Market Research: {{research_topic}}
 
-### Market Size and Growth
+## Research Initialization
 
-[Market size and growth data with source citations]
-_Source: [URL with {{current_year}} market data]_
+### Research Understanding Confirmed
 
-### Customer Segments
+**Topic**: {{research_topic}}
+**Goals**: {{research_goals}}
+**Research Type**: Market Research
+**Data Currency**: {{current_year}} with rigorous source verification
+**Date**: {{date}}
 
-[Customer segments analysis with source citations]
-_Source: [URL with {{current_year}} segment data]_
+### Research Scope
 
-### Competitive Landscape
+**Market Analysis Focus Areas:**
 
-[Competitive landscape analysis with source citations]
-_Source: [URL with {{current_year}} competitive data]_
+- Market size, growth projections, and dynamics
+- Customer segments, behavior patterns, and insights
+- Competitive landscape and positioning analysis
+- Strategic recommendations and implementation guidance
 
-### Market Trends
+**Research Methodology:**
 
-[Market trends analysis with source citations]
-_Source: [URL with {{current_year}} trends data]_
+- Current {{current_year}} web data with source verification
+- Multiple independent sources for critical claims
+- Confidence level assessment for uncertain data
+- Comprehensive coverage with no critical gaps
 
-### Pricing and Business Models
+### Next Steps
 
-[Pricing analysis with source citations]
-_Source: [URL with {{current_year}} pricing data]_
+**Research Workflow:**
 
-### Market Opportunities
+1. ✅ Initialization and scope setting (current step)
+2. Customer Insights and Behavior Analysis
+3. Competitive Landscape Analysis
+4. Strategic Synthesis and Recommendations
 
-[Market opportunities analysis with source citations]
-_Source: [URL with {{current_year}} opportunity data]_
+**Research Status**: Scope confirmed, ready to proceed with detailed market analysis
 ```
 
-### 3. Present Analysis and Continue Option
+### 4. Present Confirmation and Continue Option
 
-Show the generated market analysis and present continue option:
-"I've completed the **market analysis** using current {{current_year}} web data with rigorous source verification.
+Show initial scope document and present continue option:
+"I've documented our understanding and initial scope for **{{research_topic}}** market research.
 
-**Key Market Findings:**
+**What I've established:**
 
-- Market size and growth projections identified
-- Customer segments clearly defined
-- Competitive landscape thoroughly analyzed
-- Market trends and opportunities documented
+- Research topic and goals confirmed
+- Market analysis focus areas defined
+- Research methodology with {{current_year}} data verification
+- Clear workflow progression
 
-**Ready to proceed to customer insights?**
-[C] Continue - Save this to the document and proceed to customer insights
+**Document Status:** Initial scope written to research file for your review
 
-### 4. Handle Continue Selection
+**Ready to begin detailed market research?**
+[C] Continue - Confirm scope and proceed to customer insights analysis
+[Modify] Suggest changes to research scope before proceeding
+
+### 5. Handle User Response
 
 #### If 'C' (Continue):
 
-- Append the final content to the research document
 - Update frontmatter: `stepsCompleted: [1]`
+- Add confirmation note to document: "Scope confirmed by user on {{date}}"
 - Load: `./step-02-customer-insights.md`
 
-## APPEND TO DOCUMENT:
+#### If 'Modify':
 
-When user selects 'C', append the content directly to the research document using the structure from step 2.
+- Gather user changes to scope
+- Update document with modifications
+- Re-present updated scope for confirmation
 
 ## SUCCESS METRICS:
 
-✅ Market size and growth data with current {{current_year}} citations
-✅ Customer segments clearly identified and analyzed
-✅ Competitive landscape thoroughly mapped
-✅ Market trends and opportunities documented
+✅ Research topic and goals accurately understood
+✅ Market research scope clearly defined
+✅ Initial scope document written immediately
+✅ User opportunity to review and modify scope
 ✅ [C] continue option presented and handled correctly
-✅ Content properly appended to document when C selected
-✅ Proper routing to customer insights step
+✅ Document properly updated with scope confirmation
 
 ## FAILURE MODES:
 
-❌ Not using {{current_year}} in market web searches
-❌ Missing critical market size or growth data
-❌ Not identifying key customer segments
-❌ Incomplete competitive landscape analysis
-❌ Not presenting [C] continue option after content generation
-❌ Appending content without user selecting 'C'
+❌ Not confirming understanding of research topic and goals
+❌ Generating research content instead of just scope clarification
+❌ Not writing initial scope document to file
+❌ Not providing opportunity for user to modify scope
+❌ Proceeding to next step without user confirmation
+❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor research decisions
+❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file
+❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols
 
-## MARKET RESEARCH PROTOCOLS:
+## INITIALIZATION PRINCIPLES:
 
-- Search for authoritative market research reports
-- Use industry association and trade publication sources
-- Cross-reference multiple sources for critical market data
-- Note regional and demographic market variations
-- Research market validation and sizing methodologies
+This step ensures:
+
+- Clear mutual understanding of research objectives
+- Well-defined research scope and approach
+- Immediate documentation for user review
+- User control over research direction before detailed work begins
 
 ## NEXT STEP:
 
-After user selects 'C' and content is saved to document, load `./step-02-customer-insights.md` to focus on customer behavior and insights.
+After user confirmation and scope finalization, load `./step-02-customer-insights.md` to begin detailed market research with customer insights analysis using {{current_year}} data and rigorous source verification.
 
-Remember: Always emphasize current {{current_year}} market data and rigorous source verification!
+Remember: Init steps confirm understanding and scope, not generate research content!

src/modules/bmm/workflows/1-analysis/research/market-steps/step-02-customer-behavior.md

@@ -0,0 +1,235 @@
+# Market Research Step 2: Customer Behavior and Segments
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+- 🛑 NEVER generate content without web search verification
+- ✅ ALWAYS use {{current_year}} web searches for current customer data
+- 📋 YOU ARE A CUSTOMER BEHAVIOR ANALYST, not content generator
+- 💬 FOCUS on customer behavior patterns and demographic analysis
+- 🔍 WEB RESEARCH REQUIRED - Use {{current_year}} data and verify sources
+- 📝 WRITE CONTENT IMMEDIATELY TO DOCUMENT
+- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete research
+- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Show web search analysis before presenting findings
+- ⚠️ Present [C] continue option after customer behavior content generation
+- 📝 WRITE CUSTOMER BEHAVIOR ANALYSIS TO DOCUMENT IMMEDIATELY
+- 💾 ONLY proceed when user chooses C (Continue)
+- 📖 Update frontmatter `stepsCompleted: [1, 2]` before loading next step
+- 🚫 FORBIDDEN to load next step until C is selected
+
+## CONTEXT BOUNDARIES:
+
+- Current document and frontmatter from step-01 are available
+- Focus on customer behavior patterns and demographic analysis
+- Web search capabilities with source verification are enabled
+- Previous step confirmed research scope and goals
+- **Research topic = "{{research_topic}}"** - established from initial discussion
+- **Research goals = "{{research_goals}}"** - established from initial discussion
+
+## YOUR TASK:
+
+Conduct customer behavior and segment analysis using current {{current_year}} web data with emphasis on patterns and demographics.
+
+## CUSTOMER BEHAVIOR ANALYSIS SEQUENCE:
+
+### 1. Begin Customer Behavior Analysis
+
+**UTILIZE SUBPROCESSES AND SUBAGENTS**: Use research subagents, subprocesses or parallel processing if available to thoroughly analyze different customer behavior areas simultaneously and thoroughly.
+
+Start with customer behavior research approach:
+"Now I'll conduct **customer behavior analysis** for **{{research_topic}}** using current {{current_year}} web data to understand customer patterns.
+
+**Customer Behavior Focus:**
+
+- Customer behavior patterns and preferences
+- Demographic profiles and segmentation
+- Psychographic characteristics and values
+- Behavior drivers and influences
+- Customer interaction patterns and engagement
+
+**Let me search for current customer behavior insights.**"
+
+### 2. Parallel Customer Behavior Research Execution
+
+**Execute multiple web searches simultaneously:**
+
+`WebSearch: "{{research_topic}} customer behavior patterns {{current_year}}"`
+`WebSearch: "{{research_topic}} customer demographics {{current_year}}"`
+`WebSearch: "{{research_topic}} psychographic profiles {{current_year}}"`
+`WebSearch: "{{research_topic}} customer behavior drivers {{current_year}}"`
+
+**Analysis approach:**
+
+- Look for customer behavior studies and research reports
+- Search for demographic segmentation and analysis
+- Research psychographic profiling and value systems
+- Analyze behavior drivers and influencing factors
+- Study customer interaction and engagement patterns
+
+### 3. Analyze and Aggregate Results
+
+**Collect and analyze findings from all parallel searches:**
+
+"After executing comprehensive parallel web searches, let me analyze and aggregate customer behavior findings:
+
+**Research Coverage:**
+
+- Customer behavior patterns and preferences
+- Demographic profiles and segmentation
+- Psychographic characteristics and values
+- Behavior drivers and influences
+- Customer interaction patterns and engagement
+
+**Cross-Behavior Analysis:**
+[Identify patterns connecting demographics, psychographics, and behaviors]
+
+**Quality Assessment:**
+[Overall confidence levels and research gaps identified]"
+
+### 4. Generate Customer Behavior Content
+
+**WRITE IMMEDIATELY TO DOCUMENT**
+
+Prepare customer behavior analysis with web search citations:
+
+#### Content Structure:
+
+When saving to document, append these Level 2 and Level 3 sections:
+
+```markdown
+## Customer Behavior and Segments
+
+### Customer Behavior Patterns
+
+[Customer behavior patterns analysis with source citations]
+_Behavior Drivers: [Key motivations and patterns from web search]_
+_Interaction Preferences: [Customer engagement and interaction patterns]_
+_Decision Habits: [How customers typically make decisions]_
+_Source: [URL with {{current_year}} customer behavior data]_
+
+### Demographic Segmentation
+
+[Demographic analysis with source citations]
+_Age Demographics: [Age groups and preferences]_
+_Income Levels: [Income segments and purchasing behavior]_
+_Geographic Distribution: [Regional/city differences]_
+_Education Levels: [Education impact on behavior]_
+_Source: [URL with {{current_year}} demographic data]_
+
+### Psychographic Profiles
+
+[Psychographic analysis with source citations]
+_Values and Beliefs: [Core values driving customer behavior]_
+_Lifestyle Preferences: [Lifestyle choices and behaviors]_
+_Attitudes and Opinions: [Customer attitudes toward products/services]_
+_Personality Traits: [Personality influences on behavior]_
+_Source: [URL with {{current_year}} psychographic data]_
+
+### Customer Segment Profiles
+
+[Detailed customer segment profiles with source citations]
+_Segment 1: [Detailed profile including demographics, psychographics, behavior]_
+_Segment 2: [Detailed profile including demographics, psychographics, behavior]_
+_Segment 3: [Detailed profile including demographics, psychographics, behavior]_
+_Source: [URL with {{current_year}} segment data]_
+
+### Behavior Drivers and Influences
+
+[Behavior drivers analysis with source citations]
+_Emotional Drivers: [Emotional factors influencing behavior]_
+_Rational Drivers: [Logical decision factors]_
+_Social Influences: [Social and peer influences]_
+_Economic Influences: [Economic factors affecting behavior]_
+_Source: [URL with {{current_year}} behavior drivers data]_
+
+### Customer Interaction Patterns
+
+[Customer interaction analysis with source citations]
+_Research and Discovery: [How customers find and research options]_
+_Purchase Decision Process: [Steps in purchase decision making]_
+_Post-Purchase Behavior: [After-purchase engagement patterns]_
+_Loyalty and Retention: [Factors driving customer loyalty]_
+_Source: [URL with {{current_year}} interaction data]_
+```
+
+### 5. Present Analysis and Continue Option
+
+**Show analysis and present continue option:**
+
+"I've completed **customer behavior analysis** using current {{current_year}} data to understand customer patterns for {{research_topic}}.
+
+**Key Customer Behavior Findings:**
+
+- Customer behavior patterns clearly identified with drivers
+- Demographic segmentation thoroughly analyzed
+- Psychographic profiles mapped and documented
+- Customer interaction patterns captured
+- Multiple sources verified for critical insights
+
+**Ready to proceed to customer pain points?**
+[C] Continue - Save this to document and proceed to pain points analysis
+
+### 6. Handle Continue Selection
+
+#### If 'C' (Continue):
+
+- **CONTENT ALREADY WRITTEN TO DOCUMENT**
+- Update frontmatter: `stepsCompleted: [1, 2]`
+- Load: `./step-03-customer-pain-points.md`
+
+## APPEND TO DOCUMENT:
+
+Content is already written to document when generated in step 4. No additional append needed.
+
+## SUCCESS METRICS:
+
+✅ Customer behavior patterns identified with current {{current_year}} citations
+✅ Demographic segmentation thoroughly analyzed
+✅ Psychographic profiles clearly documented
+✅ Customer interaction patterns captured
+✅ Multiple sources verified for critical insights
+✅ Content written immediately to document
+✅ [C] continue option presented and handled correctly
+✅ Proper routing to next step (customer pain points)
+✅ Research goals alignment maintained
+
+## FAILURE MODES:
+
+❌ Not using {{current_year}} in customer web searches
+❌ Missing critical customer behavior patterns
+❌ Incomplete demographic segmentation analysis
+❌ Missing psychographic profile documentation
+❌ Not writing content immediately to document
+❌ Not presenting [C] continue option after content generation
+❌ Not routing to customer pain points analysis step
+❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor research decisions
+❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file
+❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols
+
+## CUSTOMER BEHAVIOR RESEARCH PROTOCOLS:
+
+- Research customer behavior studies and market research
+- Use demographic data from authoritative sources
+- Research psychographic profiling and value systems
+- Analyze customer interaction and engagement patterns
+- Focus on current {{current_year}} behavior data and trends
+- Present conflicting information when sources disagree
+- Apply confidence levels appropriately
+
+## BEHAVIOR ANALYSIS STANDARDS:
+
+- Always cite URLs for web search results
+- Use authoritative customer research sources
+- Note data currency and potential limitations
+- Present multiple perspectives when sources conflict
+- Apply confidence levels to uncertain data
+- Focus on actionable customer insights
+
+## NEXT STEP:
+
+After user selects 'C', load `./step-03-customer-pain-points.md` to analyze customer pain points, challenges, and unmet needs for {{research_topic}}.
+
+Remember: Always write research content to document immediately and emphasize current {{current_year}} customer data with rigorous source verification!

src/modules/bmm/workflows/1-analysis/research/market-steps/step-02-customer-insights.md

@@ -3,6 +3,9 @@
 ## MANDATORY EXECUTION RULES (READ FIRST):
 
 - 🛑 NEVER generate content without web search verification
+
+- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions
+- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding
 - ✅ ALWAYS use {{current_year}} web searches for current customer data
 - 📋 YOU ARE A CUSTOMER INSIGHTS ANALYST, not content generator
 - 💬 FOCUS on customer behavior and needs analysis
@@ -176,6 +179,10 @@ When user selects 'C', append the content directly to the research document usin
 ❌ Not presenting [C] continue option after content generation
 ❌ Appending content without user selecting 'C'
 
+❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions
+❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file
+❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols
+
 ## CUSTOMER RESEARCH PROTOCOLS:
 
 - Search for customer behavior studies and surveys

src/modules/bmm/workflows/1-analysis/research/market-steps/step-03-customer-pain-points.md

@@ -0,0 +1,247 @@
+# Market Research Step 3: Customer Pain Points and Needs
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+- 🛑 NEVER generate content without web search verification
+
+- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions
+- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding
+- ✅ ALWAYS use {{current_year}} web searches for current customer data
+- 📋 YOU ARE A CUSTOMER NEEDS ANALYST, not content generator
+- 💬 FOCUS on customer pain points, challenges, and unmet needs
+- 🔍 WEB RESEARCH REQUIRED - Use {{current_year}} data and verify sources
+- 📝 WRITE CONTENT IMMEDIATELY TO DOCUMENT
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Show web search analysis before presenting findings
+- ⚠️ Present [C] continue option after pain points content generation
+- 📝 WRITE CUSTOMER PAIN POINTS ANALYSIS TO DOCUMENT IMMEDIATELY
+- 💾 ONLY proceed when user chooses C (Continue)
+- 📖 Update frontmatter `stepsCompleted: [1, 2, 3]` before loading next step
+- 🚫 FORBIDDEN to load next step until C is selected
+
+## CONTEXT BOUNDARIES:
+
+- Current document and frontmatter from previous steps are available
+- Customer behavior analysis completed in previous step
+- Focus on customer pain points, challenges, and unmet needs
+- Web search capabilities with source verification are enabled
+- **Research topic = "{{research_topic}}"** - established from initial discussion
+- **Research goals = "{{research_goals}}"** - established from initial discussion
+
+## YOUR TASK:
+
+Conduct customer pain points and needs analysis using current {{current_year}} web data with emphasis on challenges and frustrations.
+
+## CUSTOMER PAIN POINTS ANALYSIS SEQUENCE:
+
+### 1. Begin Customer Pain Points Analysis
+
+**UTILIZE SUBPROCESSES AND SUBAGENTS**: Use research subagents, subprocesses or parallel processing if available to thoroughly analyze different customer pain point areas simultaneously and thoroughly.
+
+Start with customer pain points research approach:
+"Now I'll conduct **customer pain points analysis** for **{{research_topic}}** using current {{current_year}} web data to understand customer challenges.
+
+**Customer Pain Points Focus:**
+
+- Customer challenges and frustrations
+- Unmet needs and unaddressed problems
+- Barriers to adoption or usage
+- Service and support pain points
+- Customer satisfaction gaps
+
+**Let me search for current customer pain points insights.**"
+
+### 2. Parallel Pain Points Research Execution
+
+**Execute multiple web searches simultaneously:**
+
+`WebSearch: "{{research_topic}} customer pain points challenges {{current_year}}"`
+`WebSearch: "{{research_topic}} customer frustrations {{current_year}}"`
+`WebSearch: "{{research_topic}} unmet customer needs {{current_year}}"`
+`WebSearch: "{{research_topic}} customer barriers to adoption {{current_year}}"`
+
+**Analysis approach:**
+
+- Look for customer satisfaction surveys and reports
+- Search for customer complaints and reviews
+- Research customer support and service issues
+- Analyze barriers to customer adoption
+- Study unmet needs and market gaps
+
+### 3. Analyze and Aggregate Results
+
+**Collect and analyze findings from all parallel searches:**
+
+"After executing comprehensive parallel web searches, let me analyze and aggregate customer pain points findings:
+
+**Research Coverage:**
+
+- Customer challenges and frustrations
+- Unmet needs and unaddressed problems
+- Barriers to adoption or usage
+- Service and support pain points
+
+**Cross-Pain Points Analysis:**
+[Identify patterns connecting different types of pain points]
+
+**Quality Assessment:**
+[Overall confidence levels and research gaps identified]"
+
+### 4. Generate Customer Pain Points Content
+
+**WRITE IMMEDIATELY TO DOCUMENT**
+
+Prepare customer pain points analysis with web search citations:
+
+#### Content Structure:
+
+When saving to document, append these Level 2 and Level 3 sections:
+
+```markdown
+## Customer Pain Points and Needs
+
+### Customer Challenges and Frustrations
+
+[Customer challenges analysis with source citations]
+_Primary Frustrations: [Major customer frustrations identified]_
+_Usage Barriers: [Barriers preventing effective usage]_
+_Service Pain Points: [Customer service and support issues]_
+_Frequency Analysis: [How often these challenges occur]_
+_Source: [URL with {{current_year}} customer challenges data]_
+
+### Unmet Customer Needs
+
+[Unmet needs analysis with source citations]
+_Critical Unmet Needs: [Most important unaddressed needs]_
+_Solution Gaps: [Opportunities to address unmet needs]_
+_Market Gaps: [Market opportunities from unmet needs]_
+_Priority Analysis: [Which needs are most critical]_
+_Source: [URL with {{current_year}} unmet needs data]_
+
+### Barriers to Adoption
+
+[Adoption barriers analysis with source citations]
+_Price Barriers: [Cost-related barriers to adoption]_
+_Technical Barriers: [Complexity or technical barriers]_
+_Trust Barriers: [Trust and credibility issues]_
+_Convenience Barriers: [Ease of use or accessibility issues]_
+_Source: [URL with {{current_year}} adoption barriers data]_
+
+### Service and Support Pain Points
+
+[Service pain points analysis with source citations]
+_Customer Service Issues: [Common customer service problems]_
+_Support Gaps: [Areas where customer support is lacking]_
+_Communication Issues: [Communication breakdowns and frustrations]_
+_Response Time Issues: [Slow response and resolution problems]_
+_Source: [URL with {{current_year}} service pain points data]_
+
+### Customer Satisfaction Gaps
+
+[Satisfaction gap analysis with source citations]
+_Expectation Gaps: [Differences between expectations and reality]_
+_Quality Gaps: [Areas where quality expectations aren't met]_
+_Value Perception Gaps: [Perceived value vs actual value]_
+_Trust and Credibility Gaps: [Trust issues affecting satisfaction]_
+_Source: [URL with {{current_year}} satisfaction gap data]_
+
+### Emotional Impact Assessment
+
+[Emotional impact analysis with source citations]
+_Frustration Levels: [Customer frustration severity assessment]_
+_Loyalty Risks: [How pain points affect customer loyalty]_
+_Reputation Impact: [Impact on brand or product reputation]_
+_Customer Retention Risks: [Risk of customer loss from pain points]_
+_Source: [URL with {{current_year}} emotional impact data]_
+
+### Pain Point Prioritization
+
+[Pain point prioritization with source citations]
+_High Priority Pain Points: [Most critical pain points to address]_
+_Medium Priority Pain Points: [Important but less critical pain points]_
+_Low Priority Pain Points: [Minor pain points with lower impact]_
+_Opportunity Mapping: [Pain points with highest solution opportunity]_
+_Source: [URL with {{current_year}} prioritization data]_
+```
+
+### 5. Present Analysis and Continue Option
+
+**Show analysis and present continue option:**
+
+"I've completed **customer pain points analysis** using current {{current_year}} data to understand customer challenges for {{research_topic}}.
+
+**Key Pain Points Findings:**
+
+- Customer challenges and frustrations thoroughly documented
+- Unmet needs and solution gaps clearly identified
+- Adoption barriers and service pain points analyzed
+- Customer satisfaction gaps assessed
+- Pain points prioritized by impact and opportunity
+
+**Ready to proceed to customer decision processes?**
+[C] Continue - Save this to document and proceed to decision processes analysis
+
+### 6. Handle Continue Selection
+
+#### If 'C' (Continue):
+
+- **CONTENT ALREADY WRITTEN TO DOCUMENT**
+- Update frontmatter: `stepsCompleted: [1, 2, 3]`
+- Load: `./step-04-customer-decisions.md`
+
+## APPEND TO DOCUMENT:
+
+Content is already written to document when generated in step 4. No additional append needed.
+
+## SUCCESS METRICS:
+
+✅ Customer challenges and frustrations clearly documented
+✅ Unmet needs and solution gaps identified
+✅ Adoption barriers and service pain points analyzed
+✅ Customer satisfaction gaps assessed
+✅ Pain points prioritized by impact and opportunity
+✅ Content written immediately to document
+✅ [C] continue option presented and handled correctly
+✅ Proper routing to next step (customer decisions)
+✅ Research goals alignment maintained
+
+## FAILURE MODES:
+
+❌ Not using {{current_year}} in customer web searches
+❌ Missing critical customer challenges or frustrations
+❌ Not identifying unmet needs or solution gaps
+❌ Incomplete adoption barriers analysis
+❌ Not writing content immediately to document
+❌ Not presenting [C] continue option after content generation
+❌ Not routing to customer decisions analysis step
+
+❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions
+❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file
+❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols
+
+## CUSTOMER PAIN POINTS RESEARCH PROTOCOLS:
+
+- Research customer satisfaction surveys and reviews
+- Use customer feedback and complaint data
+- Analyze customer support and service issues
+- Study barriers to customer adoption
+- Focus on current {{current_year}} pain point data
+- Present conflicting information when sources disagree
+- Apply confidence levels appropriately
+
+## PAIN POINTS ANALYSIS STANDARDS:
+
+- Always cite URLs for web search results
+- Use authoritative customer research sources
+- Note data currency and potential limitations
+- Present multiple perspectives when sources conflict
+- Apply confidence levels to uncertain data
+- Focus on actionable pain point insights
+
+## NEXT STEP:
+
+After user selects 'C', load `./step-04-customer-decisions.md` to analyze customer decision processes, journey mapping, and decision factors for {{research_topic}}.
+
+Remember: Always write research content to document immediately and emphasize current {{current_year}} customer pain points data with rigorous source verification!

src/modules/bmm/workflows/1-analysis/research/market-steps/step-04-customer-decisions.md

@@ -0,0 +1,257 @@
+# Market Research Step 4: Customer Decisions and Journey
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+- 🛑 NEVER generate content without web search verification
+
+- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions
+- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding
+- ✅ ALWAYS use {{current_year}} web searches for current customer data
+- 📋 YOU ARE A CUSTOMER DECISION ANALYST, not content generator
+- 💬 FOCUS on customer decision processes and journey mapping
+- 🔍 WEB RESEARCH REQUIRED - Use {{current_year}} data and verify sources
+- 📝 WRITE CONTENT IMMEDIATELY TO DOCUMENT
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Show web search analysis before presenting findings
+- ⚠️ Present [C] continue option after decision processes content generation
+- 📝 WRITE CUSTOMER DECISIONS ANALYSIS TO DOCUMENT IMMEDIATELY
+- 💾 ONLY proceed when user chooses C (Continue)
+- 📖 Update frontmatter `stepsCompleted: [1, 2, 3, 4]` before loading next step
+- 🚫 FORBIDDEN to load next step until C is selected
+
+## CONTEXT BOUNDARIES:
+
+- Current document and frontmatter from previous steps are available
+- Customer behavior and pain points analysis completed in previous steps
+- Focus on customer decision processes and journey mapping
+- Web search capabilities with source verification are enabled
+- **Research topic = "{{research_topic}}"** - established from initial discussion
+- **Research goals = "{{research_goals}}"** - established from initial discussion
+
+## YOUR TASK:
+
+Conduct customer decision processes and journey analysis using current {{current_year}} web data with emphasis on decision factors and journey mapping.
+
+## CUSTOMER DECISIONS ANALYSIS SEQUENCE:
+
+### 1. Begin Customer Decisions Analysis
+
+**UTILIZE SUBPROCESSES AND SUBAGENTS**: Use research subagents, subprocesses or parallel processing if available to thoroughly analyze different customer decision areas simultaneously and thoroughly.
+
+Start with customer decisions research approach:
+"Now I'll conduct **customer decision processes analysis** for **{{research_topic}}** using current {{current_year}} web data to understand customer decision-making.
+
+**Customer Decisions Focus:**
+
+- Customer decision-making processes
+- Decision factors and criteria
+- Customer journey mapping
+- Purchase decision influencers
+- Information gathering patterns
+
+**Let me search for current customer decision insights.**"
+
+### 2. Parallel Decisions Research Execution
+
+**Execute multiple web searches simultaneously:**
+
+`WebSearch: "{{research_topic}} customer decision process {{current_year}}"`
+`WebSearch: "{{research_topic}} buying criteria factors {{current_year}}"`
+`WebSearch: "{{research_topic}} customer journey mapping {{current_year}}"`
+`WebSearch: "{{research_topic}} decision influencing factors {{current_year}}"`
+
+**Analysis approach:**
+
+- Look for customer decision research studies
+- Search for buying criteria and factor analysis
+- Research customer journey mapping methodologies
+- Analyze decision influence factors and channels
+- Study information gathering and evaluation patterns
+
+### 3. Analyze and Aggregate Results
+
+**Collect and analyze findings from all parallel searches:**
+
+"After executing comprehensive parallel web searches, let me analyze and aggregate customer decision findings:
+
+**Research Coverage:**
+
+- Customer decision-making processes
+- Decision factors and criteria
+- Customer journey mapping
+- Decision influence factors
+
+**Cross-Decisions Analysis:**
+[Identify patterns connecting decision factors and journey stages]
+
+**Quality Assessment:**
+[Overall confidence levels and research gaps identified]"
+
+### 4. Generate Customer Decisions Content
+
+**WRITE IMMEDIATELY TO DOCUMENT**
+
+Prepare customer decisions analysis with web search citations:
+
+#### Content Structure:
+
+When saving to document, append these Level 2 and Level 3 sections:
+
+```markdown
+## Customer Decision Processes and Journey
+
+### Customer Decision-Making Processes
+
+[Decision processes analysis with source citations]
+_Decision Stages: [Key stages in customer decision making]_
+_Decision Timelines: [Timeframes for different decisions]_
+_Complexity Levels: [Decision complexity assessment]_
+_Evaluation Methods: [How customers evaluate options]_
+_Source: [URL with {{current_year}} decision process data]_
+
+### Decision Factors and Criteria
+
+[Decision factors analysis with source citations]
+_Primary Decision Factors: [Most important factors in decisions]_
+_Secondary Decision Factors: [Supporting factors influencing decisions]_
+_Weighing Analysis: [How different factors are weighed]_
+_Evoluton Patterns: [How factors change over time]_
+_Source: [URL with {{current_year}} decision factors data]_
+
+### Customer Journey Mapping
+
+[Journey mapping analysis with source citations]
+_Awareness Stage: [How customers become aware of {{research_topic}}]_
+_Consideration Stage: [Evaluation and comparison process]_
+_Decision Stage: [Final decision-making process]_
+_Purchase Stage: [Purchase execution and completion]_
+_Post-Purchase Stage: [Post-decision evaluation and behavior]_
+_Source: [URL with {{current_year}} journey mapping data]_
+
+### Touchpoint Analysis
+
+[Touchpoint analysis with source citations]
+_Digital Touchpoints: [Online and digital interaction points]_
+_Offline Touchpoints: [Physical and in-person interaction points]_
+_Information Sources: [Where customers get information]_
+_Influence Channels: [What influences customer decisions]_
+_Source: [URL with {{current_year}} touchpoint data]_
+
+### Information Gathering Patterns
+
+[Information patterns analysis with source citations]
+_Research Methods: [How customers research options]_
+_Information Sources Trusted: [Most trusted information sources]_
+_Research Duration: [Time spent gathering information]_
+_Evaluation Criteria: [How customers evaluate information]_
+_Source: [URL with {{current_year}} information gathering data]_
+
+### Decision Influencers
+
+[Decision influencer analysis with source citations]
+_Peer Influence: [How friends and family influence decisions]_
+_Expert Influence: [How expert opinions affect decisions]_
+_Media Influence: [How media and marketing affect decisions]_
+_Social Proof Influence: [How reviews and testimonials affect decisions]_
+_Source: [URL with {{current_year}} decision influencer data]_
+
+### Purchase Decision Factors
+
+[Purchase decision factors analysis with source citations]
+_Immediate Purchase Drivers: [Factors triggering immediate purchase]_
+_Delayed Purchase Drivers: [Factors causing purchase delays]_
+_Brand Loyalty Factors: [Factors driving repeat purchases]_
+_Price Sensitivity: [How price affects purchase decisions]_
+_Source: [URL with {{current_year}} purchase decision data]_
+
+### Customer Decision Optimizations
+
+[Decision optimization analysis with source citations]
+_Friction Reduction: [Ways to make decisions easier]_
+_Trust Building: [Building customer trust in decisions]_
+_Conversion Optimization: [Optimizing decision-to-purchase rates]_
+_Loyalty Building: [Building long-term customer relationships]_
+_Source: [URL with {{current_year}} decision optimization data]_
+```
+
+### 5. Present Analysis and Continue Option
+
+**Show analysis and present continue option:**
+
+"I've completed **customer decision processes analysis** using current {{current_year}} data to understand customer decision-making for {{research_topic}}.
+
+**Key Decision Findings:**
+
+- Customer decision-making processes clearly mapped
+- Decision factors and criteria thoroughly analyzed
+- Customer journey mapping completed across all stages
+- Decision influencers and touchpoints identified
+- Information gathering patterns documented
+
+**Ready to proceed to competitive analysis?**
+[C] Continue - Save this to document and proceed to competitive analysis
+
+### 6. Handle Continue Selection
+
+#### If 'C' (Continue):
+
+- **CONTENT ALREADY WRITTEN TO DOCUMENT**
+- Update frontmatter: `stepsCompleted: [1, 2, 3, 4]`
+- Load: `./step-05-competitive-analysis.md`
+
+## APPEND TO DOCUMENT:
+
+Content is already written to document when generated in step 4. No additional append needed.
+
+## SUCCESS METRICS:
+
+✅ Customer decision-making processes clearly mapped
+✅ Decision factors and criteria thoroughly analyzed
+✅ Customer journey mapping completed across all stages
+✅ Decision influencers and touchpoints identified
+✅ Information gathering patterns documented
+✅ Content written immediately to document
+✅ [C] continue option presented and handled correctly
+✅ Proper routing to next step (competitive analysis)
+✅ Research goals alignment maintained
+
+## FAILURE MODES:
+
+❌ Not using {{current_year}} in customer web searches
+❌ Missing critical decision-making process stages
+❌ Not identifying key decision factors
+❌ Incomplete customer journey mapping
+❌ Not writing content immediately to document
+❌ Not presenting [C] continue option after content generation
+❌ Not routing to competitive analysis step
+
+❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions
+❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file
+❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols
+
+## CUSTOMER DECISIONS RESEARCH PROTOCOLS:
+
+- Research customer decision studies and psychology
+- Use customer journey mapping methodologies
+- Analyze buying criteria and decision factors
+- Study decision influence and touchpoint analysis
+- Focus on current {{current_year}} decision data
+- Present conflicting information when sources disagree
+- Apply confidence levels appropriately
+
+## DECISION ANALYSIS STANDARDS:
+
+- Always cite URLs for web search results
+- Use authoritative customer decision research sources
+- Note data currency and potential limitations
+- Present multiple perspectives when sources conflict
+- Apply confidence levels to uncertain data
+- Focus on actionable decision insights
+
+## NEXT STEP:
+
+After user selects 'C', load `./step-05-competitive-analysis.md` to analyze competitive landscape, market positioning, and competitive strategies for {{research_topic}}.
+
+Remember: Always write research content to document immediately and emphasize current {{current_year}} customer decision data with rigorous source verification!

src/modules/bmm/workflows/1-analysis/research/market-steps/step-05-competitive-analysis.md

@@ -1,8 +1,11 @@
-# Market Research Step 3: Competitive Analysis
+# Market Research Step 5: Competitive Analysis
 
 ## MANDATORY EXECUTION RULES (READ FIRST):
 
 - 🛑 NEVER generate content without web search verification
+
+- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions
+- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding
 - ✅ ALWAYS use {{current_year}} web searches for current competitive data
 - 📋 YOU ARE A COMPETITIVE ANALYST, not content generator
 - 💬 FOCUS on competitive landscape and market positioning
@@ -13,7 +16,7 @@
 - 🎯 Show web search analysis before presenting findings
 - ⚠️ Present [C] complete option after competitive analysis content generation
 - 💾 ONLY save when user chooses C (Complete)
-- 📖 Update frontmatter `stepsCompleted: [1, 2, 3]` before completing workflow
+- 📖 Update frontmatter `stepsCompleted: [1, 2, 3, 4, 5]` before completing workflow
 - 🚫 FORBIDDEN to complete workflow until C is selected
 
 ## CONTEXT BOUNDARIES:
@@ -139,6 +142,10 @@ When user selects 'C', append the content directly to the research document usin
 ❌ Not presenting completion option for research workflow
 ❌ Appending content without user selecting 'C'
 
+❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions
+❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file
+❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols
+
 ## COMPETITIVE RESEARCH PROTOCOLS:
 
 - Search for industry reports and competitive intelligence

src/modules/bmm/workflows/1-analysis/research/market-steps/step-06-research-completion.md

@@ -1,8 +1,11 @@
-# Market Research Step 4: Research Completion
+# Market Research Step 6: Research Completion
 
 ## MANDATORY EXECUTION RULES (READ FIRST):
 
 - 🛑 NEVER generate content without web search verification
+
+- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions
+- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding
 - ✅ ALWAYS use {{current_year}} web searches for current market data
 - 📋 YOU ARE A MARKET RESEARCH STRATEGIST, not content generator
 - 💬 FOCUS on strategic recommendations and actionable insights
@@ -13,7 +16,7 @@
 - 🎯 Show web search analysis before presenting findings
 - ⚠️ Present [C] complete option after completion content generation
 - 💾 ONLY save when user chooses C (Complete)
-- 📖 Update frontmatter `stepsCompleted: [1, 2, 3, 4]` before completing workflow
+- 📖 Update frontmatter `stepsCompleted: [1, 2, 3, 4, 5, 6]` before completing workflow
 - 🚫 FORBIDDEN to complete workflow until C is selected
 - 📚 GENERATE COMPLETE DOCUMENT STRUCTURE with intro, TOC, and summary
 
@@ -22,7 +25,7 @@
 - Current document and frontmatter from previous steps are available
 - **Research topic = "{{research_topic}}"** - comprehensive market analysis
 - **Research goals = "{{research_goals}}"** - achieved through exhaustive market research
-- All market research sections have been completed (customer insights, competitive analysis)
+- All market research sections have been completed (customer behavior, pain points, decisions, competitive analysis)
 - Web search capabilities with source verification are enabled
 - This is the final synthesis step producing the complete market research document
 
@@ -417,6 +420,10 @@ When user selects 'C', append the content directly to the research document usin
 ❌ Producing market document without professional structure
 ❌ Not presenting completion option for final market document
 
+❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions
+❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file
+❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols
+
 ## STRATEGIC RESEARCH PROTOCOLS:
 
 - Search for current market strategy frameworks and best practices

src/modules/bmm/workflows/1-analysis/research/technical-steps/step-01-init.md

@@ -1,203 +1,136 @@
-# Technical Research Step 1: Technical Initialization
+# Technical Research Step 1: Technical Research Scope Confirmation
 
 ## MANDATORY EXECUTION RULES (READ FIRST):
 
-- 🛑 NEVER generate content without user input
-- ✅ ALWAYS use {{current_year}} web searches for current technical data
-- 📋 YOU ARE A TECHNICAL ANALYST, not content generator
-- 💬 FOCUS on technical architecture and implementation patterns
-- 🔍 WEB RESEARCH REQUIRED - Use {{current_year}} data and verify sources
+- 🛑 NEVER generate content without user confirmation
+
+- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions
+- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding
+- ✅ FOCUS EXCLUSIVELY on confirming technical research scope and approach
+- 📋 YOU ARE A TECHNICAL RESEARCH PLANNER, not content generator
+- 💬 ACKNOWLEDGE and CONFIRM understanding of technical research goals
+- 🔍 This is SCOPE CONFIRMATION ONLY - no web research yet
 
 ## EXECUTION PROTOCOLS:
 
-- 🎯 Show web search analysis before presenting findings
-- ⚠️ Present [C] continue option after technical overview content generation
-- 💾 ONLY save when user chooses C (Continue)
+- 🎯 Show your analysis before taking any action
+- ⚠️ Present [C] continue option after scope confirmation
+- 💾 ONLY proceed when user chooses C (Continue)
 - 📖 Update frontmatter `stepsCompleted: [1]` before loading next step
 - 🚫 FORBIDDEN to load next step until C is selected
 
 ## CONTEXT BOUNDARIES:
 
-- Current document and frontmatter from main workflow discovery are available
 - Research type = "technical" is already set
 - **Research topic = "{{research_topic}}"** - discovered from initial discussion
 - **Research goals = "{{research_goals}}"** - captured from initial discussion
-- Focus on technical research with current {{current_year}} data
-- Web search capabilities with source verification are enabled
+- Focus on technical architecture and implementation research
+- Web search capabilities with {{current_year}} data are enabled
 
 ## YOUR TASK:
 
-Initialize technical research scope and approach for the already-identified topic: **{{research_topic}}** with goals: {{research_goals}}
+Confirm technical research scope and approach for **{{research_topic}}** with the user's goals in mind.
 
-## TECHNICAL OVERVIEW SEQUENCE:
+## TECHNICAL SCOPE CONFIRMATION:
 
-### 1. Initialize Technical Research
+### 1. Begin Scope Confirmation
 
-Start with technical-specific positioning:
-"I'll guide you through **technical research** for **{{research_topic}}** using current {{current_year}} web data with rigorous source verification.
+Start with technical scope understanding:
+"I understand you want to conduct **technical research** for **{{research_topic}}** with these goals: {{research_goals}}
 
-**Research Goals Identified:** {{research_goals}}
+**Technical Research Scope:**
 
-**Technical Research Focus for {{research_topic}}:**
+- **Architecture Analysis**: System design patterns, frameworks, and architectural decisions
+- **Implementation Approaches**: Development methodologies, coding patterns, and best practices
+- **Technology Stack**: Languages, frameworks, tools, and platforms relevant to {{research_topic}}
+- **Integration Patterns**: APIs, communication protocols, and system interoperability
+- **Performance Considerations**: Scalability, optimization, and performance patterns
 
-- Technical architecture patterns and frameworks relevant to {{research_topic}}
-- Implementation approaches and best practices for {{research_topic}}
-- Technology stack evolution and trends affecting {{research_topic}}
-- Integration patterns and interoperability for {{research_topic}}
-- Performance and scalability considerations for {{research_topic}}
+**Research Approach:**
 
-Let me refine the technical research scope specifically for **{{research_topic}}**:
+- Current {{current_year}} web data with rigorous source verification
+- Multi-source validation for critical technical claims
+- Confidence levels for uncertain technical information
+- Comprehensive technical coverage with architecture-specific insights
 
-### 2. Establish Technical Research Context
+### 2. Scope Confirmation
 
-#### Technical Context Questions:
+Present clear scope confirmation:
+"**Technical Research Scope Confirmation:**
 
-- "What technical aspects of {{research_topic}} are most critical for your goals?"
-- "Are there particular technologies or platforms within {{research_topic}} we should focus on?"
-- "Should we analyze current state of {{research_topic}} or include future technical trends?"
-- "What depth of technical analysis do you need for {{research_topic}} - overview or comprehensive?"
-- "Are there specific integration or implementation concerns for {{research_topic}}?"
+For **{{research_topic}}**, I will research:
 
-### 3. Begin Technical Research Execution
+✅ **Architecture Analysis** - design patterns, frameworks, system architecture
+✅ **Implementation Approaches** - development methodologies, coding patterns
+✅ **Technology Stack** - languages, frameworks, tools, platforms
+✅ **Integration Patterns** - APIs, protocols, interoperability
+✅ **Performance Considerations** - scalability, optimization, patterns
 
-After scope refinement, proceed with:
+**All using current {{current_year}} web data with source verification.**
 
-### 2. Web Search for Technical Architecture
+**Does this technical research scope and approach align with your goals?**
+[C] Continue - Begin technical research with this scope
 
-Search for current architecture patterns:
-`WebSearch: "[technology/domain] architecture patterns frameworks {{current_year}}"`
-
-**Architecture focus:**
-
-- Current architectural patterns and design principles
-- Frameworks and platforms commonly used
-- Microservices, monolith, and hybrid approaches
-- Cloud-native and edge computing patterns
-
-### 3. Web Search for Implementation Approaches
-
-Search for current implementation practices:
-`WebSearch: "[technology/domain] implementation best practices {{current_year}}"`
-
-**Implementation focus:**
-
-- Development methodologies and approaches
-- Code organization and structure patterns
-- Testing and quality assurance practices
-- Deployment and operations strategies
-
-### 4. Web Search for Technology Stack Trends
-
-Search for current technology trends:
-`WebSearch: "[technology/domain] technology stack trends {{current_year}}"`
-
-**Stack focus:**
-
-- Programming languages and frameworks popularity
-- Database and storage technologies
-- APIs and communication protocols
-- Development tools and platforms
-
-### 5. Generate Technical Overview Content
-
-Prepare technical analysis with web search citations:
-
-#### Content Structure:
-
-When saving to document, append these Level 2 and Level 3 sections:
-
-```markdown
-## Technical Overview
-
-### Current Architecture Patterns
-
-[Architecture patterns analysis with source citations]
-_Source: [URL with {{current_year}} architecture data]_
-
-### Implementation Approaches
-
-[Implementation approaches analysis with source citations]
-_Source: [URL with {{current_year}} implementation data]_
-
-### Technology Stack Evolution
-
-[Technology stack analysis with source citations]
-_Source: [URL with {{current_year}} technology data]_
-
-### Integration and Interoperability
-
-[Integration patterns analysis with source citations]
-_Source: [URL with {{current_year}} integration data]_
-
-### Performance and Scalability Patterns
-
-[Performance patterns analysis with source citations]
-_Source: [URL with {{current_year}} performance data]_
-
-### Development and Operations Practices
-
-[DevOps practices analysis with source citations]
-_Source: [URL with {{current_year}} DevOps data]_
-```
-
-### 6. Present Analysis and Continue Option
-
-Show the generated technical overview and present continue option:
-"I've completed the **technical overview analysis** using current {{current_year}} data to understand the technical landscape.
-
-**Key Technical Findings:**
-
-- Current architecture patterns and frameworks identified
-- Implementation approaches and best practices mapped
-- Technology stack evolution and trends documented
-- Integration patterns and interoperability analyzed
-- Performance and scalability considerations captured
-
-**Ready to proceed to architectural patterns?**
-[C] Continue - Save this to the document and move to architectural patterns
-
-### 7. Handle Continue Selection
+### 3. Handle Continue Selection
 
 #### If 'C' (Continue):
 
-- Append the final content to the research document
+- Document scope confirmation in research file
 - Update frontmatter: `stepsCompleted: [1]`
-- Load: `./step-02-technical-overview.md`
+- Load: `./step-02-technology-stack.md`
 
 ## APPEND TO DOCUMENT:
 
-When user selects 'C', append the content directly to the research document using the structure from step 5.
+When user selects 'C', append scope confirmation:
+
+```markdown
+## Technical Research Scope Confirmation
+
+**Research Topic:** {{research_topic}}
+**Research Goals:** {{research_goals}}
+
+**Technical Research Scope:**
+
+- Architecture Analysis - design patterns, frameworks, system architecture
+- Implementation Approaches - development methodologies, coding patterns
+- Technology Stack - languages, frameworks, tools, platforms
+- Integration Patterns - APIs, protocols, interoperability
+- Performance Considerations - scalability, optimization, patterns
+
+**Research Methodology:**
+
+- Current {{current_year}} web data with rigorous source verification
+- Multi-source validation for critical technical claims
+- Confidence level framework for uncertain information
+- Comprehensive technical coverage with architecture-specific insights
+
+**Scope Confirmed:** {{date}}
+```
 
 ## SUCCESS METRICS:
 
-✅ Architecture patterns identified with current {{current_year}} citations
-✅ Implementation approaches clearly documented
-✅ Technology stack evolution thoroughly analyzed
-✅ Integration patterns and interoperability mapped
-✅ Performance and scalability considerations captured
+✅ Technical research scope clearly confirmed with user
+✅ All technical analysis areas identified and explained
+✅ Research methodology with {{current_year}} data emphasized
 ✅ [C] continue option presented and handled correctly
-✅ Content properly appended to document when C selected
-✅ Proper routing to architectural patterns step
+✅ Scope confirmation documented when user proceeds
+✅ Proper routing to next technical research step
 
 ## FAILURE MODES:
 
-❌ Not using {{current_year}} in technical web searches
-❌ Missing critical architecture patterns or frameworks
-❌ Not identifying current implementation best practices
-❌ Incomplete technology stack evolution analysis
-❌ Not presenting [C] continue option after content generation
-❌ Appending content without user selecting 'C'
+❌ Not clearly confirming technical research scope with user
+❌ Missing critical technical analysis areas
+❌ Not emphasizing {{current_year}} web data requirement
+❌ Not presenting [C] continue option
+❌ Proceeding without user scope confirmation
+❌ Not routing to next technical research step
 
-## TECHNICAL RESEARCH PROTOCOLS:
-
-- Search for technical documentation and architecture guides
-- Use industry technical publications and conference proceedings
-- Research open-source projects and their architectures
-- Note technology adoption patterns and migration trends
-- Research performance benchmarking and optimization techniques
+❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions
+❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file
+❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols
 
 ## NEXT STEP:
 
-After user selects 'C', load `./step-02-technical-overview.md` to focus on specific architectural patterns and design decisions.
+After user selects 'C', load `./step-02-technology-stack.md` to begin technology stack analysis with current {{current_year}} web data.
 
-Remember: Always emphasize current {{current_year}} technical data and rigorous source verification!
+Remember: This is SCOPE CONFIRMATION ONLY - no actual technical research yet, just confirming the research approach and scope!

src/modules/bmm/workflows/1-analysis/research/technical-steps/step-02-technical-overview.md

@@ -1,185 +1,237 @@
-# Technical Research Step 2: Technical Overview
+# Technical Research Step 2: Technology Stack Analysis
 
 ## MANDATORY EXECUTION RULES (READ FIRST):
 
 - 🛑 NEVER generate content without web search verification
-- ✅ ALWAYS use {{current_year}} web searches for current technical data
-- 📋 YOU ARE A TECHNICAL ANALYST, not content generator
-- 💬 FOCUS on technical architecture and implementation patterns
+
+- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions
+- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding
+- ✅ ALWAYS use {{current_year}} web searches for current technology data
+- 📋 YOU ARE A TECHNOLOGY STACK ANALYST, not content generator
+- 💬 FOCUS on languages, frameworks, tools, and platforms
 - 🔍 WEB RESEARCH REQUIRED - Use {{current_year}} data and verify sources
+- 📝 WRITE CONTENT IMMEDIATELY TO DOCUMENT
 
 ## EXECUTION PROTOCOLS:
 
 - 🎯 Show web search analysis before presenting findings
-- ⚠️ Present [C] continue option after technical overview content generation
-- 💾 ONLY save when user chooses C (Continue)
+- ⚠️ Present [C] continue option after technology stack content generation
+- 📝 WRITE TECHNOLOGY STACK ANALYSIS TO DOCUMENT IMMEDIATELY
+- 💾 ONLY proceed when user chooses C (Continue)
 - 📖 Update frontmatter `stepsCompleted: [1, 2]` before loading next step
 - 🚫 FORBIDDEN to load next step until C is selected
 
 ## CONTEXT BOUNDARIES:
 
 - Current document and frontmatter from step-01 are available
-- Focus on technical architecture and implementation landscape
+- **Research topic = "{{research_topic}}"** - established from initial discussion
+- **Research goals = "{{research_goals}}"** - established from initial discussion
+- Focus on languages, frameworks, tools, and platforms
 - Web search capabilities with source verification are enabled
-- May need to search for current technical trends and frameworks
 
 ## YOUR TASK:
 
-Conduct comprehensive technical overview using current {{current_year}} web data with emphasis on architecture patterns and implementation approaches.
+Conduct technology stack analysis focusing on languages, frameworks, tools, and platforms using current {{current_year}} web data with rigorous source verification.
 
-## TECHNICAL OVERVIEW SEQUENCE:
+## TECHNOLOGY STACK ANALYSIS SEQUENCE:
 
-### 1. Begin Technical Overview
+### 1. Begin Technology Stack Analysis
 
-**UTILIZE SUBPROCESSES AND SUBAGENTS**: Use research subagents, subprocesses or parallel processing if available to thoroughly analyze different technical areas simultaneously and thoroughly
+**UTILIZE SUBPROCESSES AND SUBAGENTS**: Use research subagents, subprocesses or parallel processing if available to thoroughly analyze different technology stack areas simultaneously and thoroughly.
 
-Start with technical research approach:
-"Now I'll conduct **technical overview analysis** using current {{current_year}} web data to understand the technical landscape for [technology/domain].
+Start with technology stack research approach:
+"Now I'll conduct **technology stack analysis** for **{{research_topic}}** using current {{current_year}} web data to understand the technology landscape.
 
-**Technical Overview Focus:**
+**Technology Stack Focus:**
 
-- Current technical architecture patterns and frameworks
-- Implementation approaches and best practices
-- Technology stack evolution and trends
-- Integration patterns and interoperability
-- Performance and scalability considerations
+- Programming languages and their evolution
+- Development frameworks and libraries
+- Database and storage technologies
+- Development tools and platforms
+- Cloud infrastructure and deployment platforms
 
-**Let me search for current technical landscape information using parallel web searches for comprehensive coverage.**"
+**Let me search for current technology stack insights.**"
 
-### 2. Parallel Technical Research Execution
+### 2. Parallel Technology Stack Research Execution
 
 **Execute multiple web searches simultaneously:**
 
-`WebSearch: "[technology/domain] architecture patterns frameworks {{current_year}}"`
-`WebSearch: "[technology/domain] implementation best practices {{current_year}}"`
-`WebSearch: "[technology/domain] technology stack trends {{current_year}}"`
+`WebSearch: "{{research_topic}} programming languages frameworks {{current_year}}"`
+`WebSearch: "{{research_topic}} development tools platforms {{current_year}}"`
+`WebSearch: "{{research_topic}} database storage technologies {{current_year}}"`
+`WebSearch: "{{research_topic}} cloud infrastructure platforms {{current_year}}"`
 
 **Analysis approach:**
 
-- Look for recent technical documentation and architecture guides
-- Search for technical publications and conference proceedings
-- Research open-source projects and their architectures
-- Note technology adoption patterns and migration trends
-- Research performance benchmarking and optimization techniques
+- Look for recent technology trend reports and developer surveys
+- Search for technology documentation and best practices
+- Research open-source projects and their technology choices
+- Analyze technology adoption patterns and migration trends
+- Study platform and tool evolution in the domain
 
 ### 3. Analyze and Aggregate Results
 
 **Collect and analyze findings from all parallel searches:**
 
-"After executing comprehensive parallel web searches, let me analyze and aggregate the technical findings:
+"After executing comprehensive parallel web searches, let me analyze and aggregate technology stack findings:
 
 **Research Coverage:**
 
-- Architecture patterns and design principles
-- Implementation approaches and methodologies
-- Technology stack evolution and current trends
+- Programming languages and frameworks analysis
+- Development tools and platforms evaluation
+- Database and storage technologies assessment
+- Cloud infrastructure and deployment platform analysis
 
-**Technical Integration Analysis:**
-[Identify how architecture patterns influence implementation approaches and technology choices]
+**Cross-Technology Analysis:**
+[Identify patterns connecting language choices, frameworks, and platform decisions]
 
 **Quality Assessment:**
 [Overall confidence levels and research gaps identified]"
 
-### 4. Generate Technical Overview Content
+### 4. Generate Technology Stack Content
 
-Prepare technical analysis with web search citations:
+**WRITE IMMEDIATELY TO DOCUMENT**
+
+Prepare technology stack analysis with web search citations:
 
 #### Content Structure:
 
 When saving to document, append these Level 2 and Level 3 sections:
 
 ```markdown
-## Technical Overview
+## Technology Stack Analysis
 
-### Current Architecture Patterns
+### Programming Languages
 
-[Architecture patterns analysis with source citations]
-_Source: [URL with {{current_year}} architecture data]_
+[Programming languages analysis with source citations]
+_Popular Languages: [Most widely used languages for {{research_topic}}]_
+_Emerging Languages: [Growing languages gaining adoption]_
+_Language Evolution: [How language preferences are changing]_
+_Performance Characteristics: [Language performance and suitability]_
+_Source: [URL with {{current_year}} language data]_
 
-### Implementation Approaches
+### Development Frameworks and Libraries
 
-[Implementation approaches analysis with source citations]
-_Source: [URL with {{current_year}} implementation data]_
+[Frameworks analysis with source citations]
+_Major Frameworks: [Dominant frameworks and their use cases]_
+_Micro-frameworks: [Lightweight options and specialized libraries]_
+_Evolution Trends: [How frameworks are evolving and changing]_
+_Ecosystem Maturity: [Library availability and community support]_
+_Source: [URL with {{current_year}} framework data]_
 
-### Technology Stack Evolution
+### Database and Storage Technologies
 
-[Technology stack analysis with source citations]
-_Source: [URL with {{current_year}} technology data]_
+[Database analysis with source citations]
+_Relational Databases: [Traditional SQL databases and their evolution]_
+_NoSQL Databases: [Document, key-value, graph, and other NoSQL options]_
+_In-Memory Databases: [Redis, Memcached, and performance-focused solutions]_
+_Data Warehousing: [Analytics and big data storage solutions]_
+_Source: [URL with {{current_year}} database data]_
 
-### Integration and Interoperability
+### Development Tools and Platforms
 
-[Integration patterns analysis with source citations]
-_Source: [URL with {{current_year}} integration data]_
+[Tools and platforms analysis with source citations]
+_IDE and Editors: [Development environments and their evolution]_
+_Version Control: [Git and related development tools]_
+_Build Systems: [Compilation, packaging, and automation tools]_
+_Testing Frameworks: [Unit testing, integration testing, and QA tools]_
+_Source: [URL with {{current_year}} tools data]_
 
-### Performance and Scalability Patterns
+### Cloud Infrastructure and Deployment
 
-[Performance patterns analysis with source citations]
-_Source: [URL with {{current_year}} performance data]_
+[Cloud platforms analysis with source citations]
+_Major Cloud Providers: [AWS, Azure, GCP and their services]_
+_Container Technologies: [Docker, Kubernetes, and orchestration]_
+_Serverless Platforms: [FaaS and event-driven computing]_
+_CDN and Edge Computing: [Content delivery and distributed computing]_
+_Source: [URL with {{current_year}} cloud data]_
 
-### Development and Operations Practices
+### Technology Adoption Trends
 
-[DevOps practices analysis with source citations]
-_Source: [URL with {{current_year}} DevOps data]_
+[Adoption trends analysis with source citations]
+_Migration Patterns: [How technology choices are evolving]_
+_Emerging Technologies: [New technologies gaining traction]_
+_Legacy Technology: [Older technologies being phased out]_
+_Community Trends: [Developer preferences and open-source adoption]_
+_Source: [URL with {{current_year}} adoption data]_
 ```
 
 ### 5. Present Analysis and Continue Option
 
-Show the generated technical overview and present continue option:
-"I've completed the **technical overview analysis** using current {{current_year}} data to understand the technical landscape.
+**Show analysis and present continue option:**
 
-**Key Technical Findings:**
+"I've completed **technology stack analysis** using current {{current_year}} data to understand the technology landscape for {{research_topic}}.
 
-- Current architecture patterns and frameworks identified
-- Implementation approaches and best practices mapped
-- Technology stack evolution and trends documented
-- Integration patterns and interoperability analyzed
-- Performance and scalability considerations captured
+**Key Technology Stack Findings:**
 
-**Ready to proceed to architectural patterns?**
-[C] Continue - Save this to the document and move to architectural patterns
+- Programming languages and frameworks thoroughly analyzed
+- Database and storage technologies evaluated
+- Development tools and platforms documented
+- Cloud infrastructure and deployment options mapped
+- Technology adoption trends identified
+
+**Ready to proceed to integration patterns analysis?**
+[C] Continue - Save this to document and proceed to integration patterns
 
 ### 6. Handle Continue Selection
 
 #### If 'C' (Continue):
 
-- Append the final content to the research document
+- **CONTENT ALREADY WRITTEN TO DOCUMENT**
 - Update frontmatter: `stepsCompleted: [1, 2]`
-- Load: `./step-03-architectural-patterns.md`
+- Load: `./step-03-integration-patterns.md`
 
 ## APPEND TO DOCUMENT:
 
-When user selects 'C', append the content directly to the research document using the structure from step 4.
+Content is already written to document when generated in step 4. No additional append needed.
 
 ## SUCCESS METRICS:
 
-✅ Architecture patterns identified with current {{current_year}} citations
-✅ Implementation approaches clearly documented
-✅ Technology stack evolution thoroughly analyzed
-✅ Integration patterns and interoperability mapped
-✅ Performance and scalability considerations captured
+✅ Programming languages and frameworks thoroughly analyzed
+✅ Database and storage technologies evaluated
+✅ Development tools and platforms documented
+✅ Cloud infrastructure and deployment options mapped
+✅ Technology adoption trends identified
+✅ Content written immediately to document
 ✅ [C] continue option presented and handled correctly
-✅ Content properly appended to document when C selected
-✅ Proper routing to architectural patterns step
+✅ Proper routing to next step (integration patterns)
+✅ Research goals alignment maintained
 
 ## FAILURE MODES:
 
-❌ Not using {{current_year}} in technical web searches
-❌ Missing critical architecture patterns or frameworks
-❌ Not identifying current implementation best practices
-❌ Incomplete technology stack evolution analysis
+❌ Not using {{current_year}} in technology web searches
+❌ Missing critical programming languages or frameworks
+❌ Incomplete database and storage technology analysis
+❌ Not identifying development tools and platforms
+❌ Not writing content immediately to document
 ❌ Not presenting [C] continue option after content generation
-❌ Appending content without user selecting 'C'
+❌ Not routing to integration patterns step
 
-## TECHNICAL RESEARCH PROTOCOLS:
+❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions
+❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file
+❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols
 
-- Search for technical documentation and architecture guides
-- Use industry technical publications and conference proceedings
-- Research open-source projects and their architectures
-- Note technology adoption patterns and migration trends
-- Research performance benchmarking and optimization techniques
+## TECHNOLOGY STACK RESEARCH PROTOCOLS:
+
+- Research technology trend reports and developer surveys
+- Use technology documentation and best practices guides
+- Analyze open-source projects and their technology choices
+- Study technology adoption patterns and migration trends
+- Focus on current {{current_year}} technology data
+- Present conflicting information when sources disagree
+- Apply confidence levels appropriately
+
+## TECHNOLOGY STACK ANALYSIS STANDARDS:
+
+- Always cite URLs for web search results
+- Use authoritative technology research sources
+- Note data currency and potential limitations
+- Present multiple perspectives when sources conflict
+- Apply confidence levels to uncertain data
+- Focus on actionable technology insights
 
 ## NEXT STEP:
 
-After user selects 'C' and content is saved to document, load `./step-03-architectural-patterns.md` to focus on specific architectural patterns and design decisions.
+After user selects 'C', load `./step-03-integration-patterns.md` to analyze APIs, communication protocols, and system interoperability for {{research_topic}}.
 
-Remember: Always emphasize current {{current_year}} technical data and rigorous source verification!
+Remember: Always write research content to document immediately and emphasize current {{current_year}} technology data with rigorous source verification!

src/modules/bmm/workflows/1-analysis/research/technical-steps/step-03-integration-patterns.md

@@ -0,0 +1,246 @@
+# Technical Research Step 3: Integration Patterns
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+- 🛑 NEVER generate content without web search verification
+
+- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions
+- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding
+- ✅ ALWAYS use {{current_year}} web searches for current integration data
+- 📋 YOU ARE AN INTEGRATION ANALYST, not content generator
+- 💬 FOCUS on APIs, protocols, and system interoperability
+- 🔍 WEB RESEARCH REQUIRED - Use {{current_year}} data and verify sources
+- 📝 WRITE CONTENT IMMEDIATELY TO DOCUMENT
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Show web search analysis before presenting findings
+- ⚠️ Present [C] continue option after integration patterns content generation
+- 📝 WRITE INTEGRATION PATTERNS ANALYSIS TO DOCUMENT IMMEDIATELY
+- 💾 ONLY proceed when user chooses C (Continue)
+- 📖 Update frontmatter `stepsCompleted: [1, 2, 3]` before loading next step
+- 🚫 FORBIDDEN to load next step until C is selected
+
+## CONTEXT BOUNDARIES:
+
+- Current document and frontmatter from previous steps are available
+- **Research topic = "{{research_topic}}"** - established from initial discussion
+- **Research goals = "{{research_goals}}"** - established from initial discussion
+- Focus on APIs, protocols, and system interoperability
+- Web search capabilities with source verification are enabled
+
+## YOUR TASK:
+
+Conduct integration patterns analysis focusing on APIs, communication protocols, and system interoperability using current {{current_year}} web data with rigorous source verification.
+
+## INTEGRATION PATTERNS ANALYSIS SEQUENCE:
+
+### 1. Begin Integration Patterns Analysis
+
+**UTILIZE SUBPROCESSES AND SUBAGENTS**: Use research subagents, subprocesses or parallel processing if available to thoroughly analyze different integration areas simultaneously and thoroughly.
+
+Start with integration patterns research approach:
+"Now I'll conduct **integration patterns analysis** for **{{research_topic}}** using current {{current_year}} web data to understand system integration approaches.
+
+**Integration Patterns Focus:**
+
+- API design patterns and protocols
+- Communication protocols and data formats
+- System interoperability approaches
+- Microservices integration patterns
+- Event-driven architectures and messaging
+
+**Let me search for current integration patterns insights.**"
+
+### 2. Parallel Integration Patterns Research Execution
+
+**Execute multiple web searches simultaneously:**
+
+`WebSearch: "{{research_topic}} API design patterns protocols {{current_year}}"`
+`WebSearch: "{{research_topic}} communication protocols data formats {{current_year}}"`
+`WebSearch: "{{research_topic}} system interoperability integration {{current_year}}"`
+`WebSearch: "{{research_topic}} microservices integration patterns {{current_year}}"`
+
+**Analysis approach:**
+
+- Look for recent API design guides and best practices
+- Search for communication protocol documentation and standards
+- Research integration platform and middleware solutions
+- Analyze microservices architecture patterns and approaches
+- Study event-driven systems and messaging patterns
+
+### 3. Analyze and Aggregate Results
+
+**Collect and analyze findings from all parallel searches:**
+
+"After executing comprehensive parallel web searches, let me analyze and aggregate integration patterns findings:
+
+**Research Coverage:**
+
+- API design patterns and protocols analysis
+- Communication protocols and data formats evaluation
+- System interoperability approaches assessment
+- Microservices integration patterns documentation
+
+**Cross-Integration Analysis:**
+[Identify patterns connecting API choices, communication protocols, and system design]
+
+**Quality Assessment:**
+[Overall confidence levels and research gaps identified]"
+
+### 4. Generate Integration Patterns Content
+
+**WRITE IMMEDIATELY TO DOCUMENT**
+
+Prepare integration patterns analysis with web search citations:
+
+#### Content Structure:
+
+When saving to document, append these Level 2 and Level 3 sections:
+
+```markdown
+## Integration Patterns Analysis
+
+### API Design Patterns
+
+[API design patterns analysis with source citations]
+_RESTful APIs: [REST principles and best practices for {{research_topic}}]_
+_GraphQL APIs: [GraphQL adoption and implementation patterns]_
+_RPC and gRPC: [High-performance API communication patterns]_
+_Webhook Patterns: [Event-driven API integration approaches]_
+_Source: [URL with {{current_year}} API design data]_
+
+### Communication Protocols
+
+[Communication protocols analysis with source citations]
+_HTTP/HTTPS Protocols: [Web-based communication patterns and evolution]_
+_WebSocket Protocols: [Real-time communication and persistent connections]_
+_Message Queue Protocols: [AMQP, MQTT, and messaging patterns]_
+_grpc and Protocol Buffers: [High-performance binary communication protocols]_
+_Source: [URL with {{current_year}} communication protocols data]_
+
+### Data Formats and Standards
+
+[Data formats analysis with source citations]
+_JSON and XML: [Structured data exchange formats and their evolution]_
+_Protobuf and MessagePack: [Efficient binary serialization formats]_
+_CSV and Flat Files: [Legacy data integration and bulk transfer patterns]_
+_Custom Data Formats: [Domain-specific data exchange standards]_
+_Source: [URL with {{current_year}} data formats data]_
+
+### System Interoperability Approaches
+
+[Interoperability analysis with source citations]
+_Point-to-Point Integration: [Direct system-to-system communication patterns]_
+_API Gateway Patterns: [Centralized API management and routing]_
+_Service Mesh: [Service-to-service communication and observability]_
+_Enterprise Service Bus: [Traditional enterprise integration patterns]_
+_Source: [URL with {{current_year}} interoperability data]_
+
+### Microservices Integration Patterns
+
+[Microservices integration analysis with source citations]
+_API Gateway Pattern: [External API management and routing]_
+_Service Discovery: [Dynamic service registration and discovery]_
+_Circuit Breaker Pattern: [Fault tolerance and resilience patterns]_
+_Saga Pattern: [Distributed transaction management]_
+_Source: [URL with {{current_year}} microservices data]_
+
+### Event-Driven Integration
+
+[Event-driven analysis with source citations]
+_Publish-Subscribe Patterns: [Event broadcasting and subscription models]_
+_Event Sourcing: [Event-based state management and persistence]_
+_Message Broker Patterns: [RabbitMQ, Kafka, and message routing]_
+_CQRS Patterns: [Command Query Responsibility Segregation]_
+_Source: [URL with {{current_year}} event-driven data]_
+
+### Integration Security Patterns
+
+[Security patterns analysis with source citations]
+_OAuth 2.0 and JWT: [API authentication and authorization patterns]_
+_API Key Management: [Secure API access and key rotation]_
+_Mutual TLS: [Certificate-based service authentication]_
+_Data Encryption: [Secure data transmission and storage]_
+_Source: [URL with {{current_year}} integration security data]_
+```
+
+### 5. Present Analysis and Continue Option
+
+**Show analysis and present continue option:**
+
+"I've completed **integration patterns analysis** using current {{current_year}} data to understand system integration approaches for {{research_topic}}.
+
+**Key Integration Patterns Findings:**
+
+- API design patterns and protocols thoroughly analyzed
+- Communication protocols and data formats evaluated
+- System interoperability approaches documented
+- Microservices integration patterns mapped
+- Event-driven integration strategies identified
+
+**Ready to proceed to architectural patterns analysis?**
+[C] Continue - Save this to document and proceed to architectural patterns
+
+### 6. Handle Continue Selection
+
+#### If 'C' (Continue):
+
+- **CONTENT ALREADY WRITTEN TO DOCUMENT**
+- Update frontmatter: `stepsCompleted: [1, 2, 3]`
+- Load: `./step-04-architectural-patterns.md`
+
+## APPEND TO DOCUMENT:
+
+Content is already written to document when generated in step 4. No additional append needed.
+
+## SUCCESS METRICS:
+
+✅ API design patterns and protocols thoroughly analyzed
+✅ Communication protocols and data formats evaluated
+✅ System interoperability approaches documented
+✅ Microservices integration patterns mapped
+✅ Event-driven integration strategies identified
+✅ Content written immediately to document
+✅ [C] continue option presented and handled correctly
+✅ Proper routing to next step (architectural patterns)
+✅ Research goals alignment maintained
+
+## FAILURE MODES:
+
+❌ Not using {{current_year}} in integration web searches
+❌ Missing critical API design patterns or protocols
+❌ Incomplete communication protocols analysis
+❌ Not identifying system interoperability approaches
+❌ Not writing content immediately to document
+❌ Not presenting [C] continue option after content generation
+❌ Not routing to architectural patterns step
+
+❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions
+❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file
+❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols
+
+## INTEGRATION PATTERNS RESEARCH PROTOCOLS:
+
+- Research API design guides and best practices documentation
+- Use communication protocol specifications and standards
+- Analyze integration platform and middleware solutions
+- Study microservices architecture patterns and case studies
+- Focus on current {{current_year}} integration data
+- Present conflicting information when sources disagree
+- Apply confidence levels appropriately
+
+## INTEGRATION PATTERNS ANALYSIS STANDARDS:
+
+- Always cite URLs for web search results
+- Use authoritative integration research sources
+- Note data currency and potential limitations
+- Present multiple perspectives when sources conflict
+- Apply confidence levels to uncertain data
+- Focus on actionable integration insights
+
+## NEXT STEP:
+
+After user selects 'C', load `./step-04-architectural-patterns.md` to analyze architectural patterns, design decisions, and system structures for {{research_topic}}.
+
+Remember: Always write research content to document immediately and emphasize current {{current_year}} integration data with rigorous source verification!

src/modules/bmm/workflows/1-analysis/research/technical-steps/step-04-architectural-patterns.md

@@ -1,31 +1,37 @@
-# Technical Research Step 3: Architectural Patterns
+# Technical Research Step 4: Architectural Patterns
 
 ## MANDATORY EXECUTION RULES (READ FIRST):
 
 - 🛑 NEVER generate content without web search verification
+
+- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions
+- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding
 - ✅ ALWAYS use {{current_year}} web searches for current architectural data
 - 📋 YOU ARE A SYSTEMS ARCHITECT, not content generator
 - 💬 FOCUS on architectural patterns and design decisions
 - 🔍 WEB RESEARCH REQUIRED - Use {{current_year}} data and verify sources
+- 📝 WRITE CONTENT IMMEDIATELY TO DOCUMENT
 
 ## EXECUTION PROTOCOLS:
 
 - 🎯 Show web search analysis before presenting findings
 - ⚠️ Present [C] continue option after architectural patterns content generation
-- 💾 ONLY save when user chooses C (Continue)
-- 📖 Update frontmatter `stepsCompleted: [1, 2, 3]` before loading next step
+- 📝 WRITE ARCHITECTURAL PATTERNS ANALYSIS TO DOCUMENT IMMEDIATELY
+- 💾 ONLY proceed when user chooses C (Continue)
+- 📖 Update frontmatter `stepsCompleted: [1, 2, 3, 4]` before loading next step
 - 🚫 FORBIDDEN to load next step until C is selected
 
 ## CONTEXT BOUNDARIES:
 
 - Current document and frontmatter from previous steps are available
+- **Research topic = "{{research_topic}}"** - established from initial discussion
+- **Research goals = "{{research_goals}}"** - established from initial discussion
 - Focus on architectural patterns and design decisions
 - Web search capabilities with source verification are enabled
-- May need to search for specific architectural frameworks and patterns
 
 ## YOUR TASK:
 
-Conduct comprehensive architectural patterns analysis using current {{current_year}} web data with emphasis on design decisions and implementation approaches.
+Conduct comprehensive architectural patterns analysis using current {{current_year}} web data with emphasis on design decisions and implementation approaches for {{research_topic}}.
 
 ## ARCHITECTURAL PATTERNS SEQUENCE:
 
@@ -175,6 +181,10 @@ When user selects 'C', append the content directly to the research document usin
 ❌ Not presenting [C] continue option after content generation
 ❌ Appending content without user selecting 'C'
 
+❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions
+❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file
+❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols
+
 ## ARCHITECTURAL RESEARCH PROTOCOLS:
 
 - Search for architecture documentation and pattern catalogs

src/modules/bmm/workflows/1-analysis/research/technical-steps/step-05-implementation-research.md

@@ -3,6 +3,9 @@
 ## MANDATORY EXECUTION RULES (READ FIRST):
 
 - 🛑 NEVER generate content without web search verification
+
+- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions
+- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding
 - ✅ ALWAYS use {{current_year}} web searches for current implementation data
 - 📋 YOU ARE AN IMPLEMENTATION ENGINEER, not content generator
 - 💬 FOCUS on implementation approaches and technology adoption
@@ -200,6 +203,10 @@ When user selects 'C', append the content directly to the research document usin
 ❌ Not presenting completion option for research workflow
 ❌ Appending content without user selecting 'C'
 
+❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions
+❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file
+❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols
+
 ## IMPLEMENTATION RESEARCH PROTOCOLS:
 
 - Search for implementation case studies and success stories

src/modules/bmm/workflows/1-analysis/research/technical-steps/step-06-research-synthesis.md

@@ -3,6 +3,9 @@
 ## MANDATORY EXECUTION RULES (READ FIRST):
 
 - 🛑 NEVER generate content without web search verification
+
+- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions
+- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding
 - ✅ ALWAYS use {{current_year}} web searches for current technical data
 - 📋 YOU ARE A TECHNICAL RESEARCH STRATEGIST, not content generator
 - 💬 FOCUS on comprehensive technical synthesis and authoritative conclusions
@@ -445,6 +448,10 @@ When user selects 'C', append the complete comprehensive technical research docu
 ❌ Producing technical document without professional structure
 ❌ Not presenting completion option for final technical document
 
+❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions
+❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file
+❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols
+
 ## COMPREHENSIVE TECHNICAL DOCUMENT STANDARDS:
 
 This step ensures the final technical research document: